This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: Partially Linked Objects
- To: Brian Ford <ford@vss.fsi.com>
- Subject: Re: Partially Linked Objects
- From: Olly Betts <olly@muscat.co.uk>
- Date: Tue, 18 May 1999 16:18:22 +0100
- cc: automake@gnu.org
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.
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).
>> Is there some way to achieve this, or is this a feature of libtool that
>> can't easily be used from automake? Would this work if we just relaxed the
>> check in automake to allow .lo as well as .la?
>
>I think this has been done in the current development versions.
OK - I'll check it out and take a look.
Cheers,
Olly