This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: rpath command?
- To: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>
- Subject: Re: rpath command?
- From: Olly Betts <olly at survex dot com>
- Date: Wed, 29 Nov 2000 18:38:32 +0000
- cc: Steve Robbins <steven dot robbins at videotron dot ca>, libtool at gnu dot org, GNU Automake List <automake at gnu dot org>
- List-Id: Discussion list for automake <automake.gnu.org><mailto:automake-request@gnu.org?subject=unsubscribe>
In message <or4s0t33n8.fsf@guarana.lsd.ic.unicamp.br>, Alexandre Oliva writes:
>[linking a library from other libraries with no object files]
>
>The point is that this just can't be done portably.
Since libtool's major purpose is to allow libraries to be built using a
portable interface, perhaps it should take care of this for the developer?
So on platforms where this doesn't work, perhaps libtool should add a dummy
file implicitly, rather than the developer having to implement the bodge
themselves?
>(ii) automake wouldn't know which compiler/linker to use for the
>library you're creating. Specifying one or more source files is
>supposed to give automake a clue on which languages are being used in
>the sub-libraries.
This would be an obstacle to libtool creating the bodge file, but the .la
file could be extended to contain information about languages used in a
libtool library.
Cheers,
Olly