Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!coolidge
From: coolidge@cs.uiuc.edu (John Coolidge)
Newsgroups: comp.windows.x
Subject: Re: Shared Libraries and Patches
Message-ID: <1990Oct4.210142.29633@julius.cs.uiuc.edu>
Date: 4 Oct 90 21:01:42 GMT
References: <9010021331.AA22861@expire.lcs.mit.edu> <9010032032.AA24339@Morgan.COM>
Sender: news@julius.cs.uiuc.edu (USENet News)
Reply-To: coolidge@cs.uiuc.edu
Organization: U of Illinois, Dept. of Computer Science, Systems Research Group
Lines: 30

jordan@morgan.COM (Jordan Hayes) writes:
>Then for the different types of shared libraries out there, you'd need
>to define a rule for SharedLibraryObjectRule in your .cf file ... Like,
>how have people hacked in shared library support for SYS V.2 machines,
>like the Intergraph that was mentioned recently or (more to my neck of
>the woods), A/UX 2.0?

This is pretty much what I did for my shared library implementation
for A/UX 2.0 (and, yes, the source patches should be out soon). The
A/UX shared library stuff is specified in macII.cf (reusing as many
of the names, and hence the Imakefile code, as possible from the Sun
code). There are some necessary changes to the Imakefiles, a few of
which are _very_ ugly :-(.

>Seems kind of weird for HasSunOSSharedLibraries to appear in a bunch of
>random files.  I thought the achitecture-independent portion of the
>rules should be in the <vendor>.cf file?

It should be. Things get confusing, though, when you add new target
files for a particular shared library architecture. For instance, in
the A/UX 2.0 stuff I've spilt out a bunch of static data in Xt and Xaw
and put it in _S<file>.o files. This adds a bunch of targets with
wierd rules, and it doesn't affect all the files in either library so
I can't just add the extra compile to the standard directives...

Of course, some of my stuff is almost certainly unnecessarily ugly...
but it works (that is, I can type 'make Makefile;make' and the right
stuff appears).

--John