Re: Partially Linked Objects

[Brian Ford <ford@vss.fsi.com>]

On Tue, 18 May 1999, Olly Betts wrote:

> In message <Pine.SGI.4.03.9905180949170.7183-100000@iscream.vss.fsi.com>, Brian
>  Ford writes:
> >Ok, so right now you can't say all.lo or all.o here, but why do you need
> >to.  all.la should work fine, it is just a name that you need to be used
> >to and understand.
> 
> But doesn't that build a libtool convenience library?  That's fine inside my
> own build system, which uses libtool.  But it won't be much use to another
> user of my library if they don't use libtool in their build system.  At
> present *none* of them do.
> 
> So what I'm trying to do is partially link all the objects into one (because
> most of the aren't directly referenced so don't work separately in an
> archive library), then put this big object in an archive library which I can
> stick in /usr/lib and anyone can use.
> 
I hadn't realized that you were actually trying to distribute this
partially linked object.  I thought it was just an intermediate step in
your build process.  Sorry.
> For the shared library it makes little difference whether I use the
> individual objects or the partially linked object (though I suspect the
> latter is going to be easier).
> 
Libtool should handle the shared library case automatically, right?

--
Brian Ford
Software Engineer
Vital Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444