Hello Alexandre,
Alexandre Oliva <[EMAIL PROTECTED]> wrote:
AO> On Sep 3, 2000, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
>> * When installing a libtool (.la) library:
>> - libfoo.la goes to $prefix/lib
>> - libfoo<iface>.dll goes to $prefix/bin
I'm glad this is acknowledged.
>> - libfoo.dll.a goes to $prefix/lib
>> - libfoo.a goes to $prefix/lib
AO> Nope. libfoo.la goes wherever -rpath specified when the library was
AO> created; it should be the same directory that is specified at install
AO> time. This is often $(libdir), but it doesn't have to be.
AO> I don't know how to arrange for an additional directory (bindir) to
AO> be specifiable without introducing an additional command-line option.
AO> Remember, libtool doesn't know about prefix, libdir or bindir, it just
AO> knows about what it's given in the command line.
You how I did it ;-) With my python re-implementation, I generate
following makefile in .libs and make it:
include ../Makefile
all:
$(INSTALL) <dll> $bindir/<dll>
So, it uses whatever bindir defined in main makefile. If you remember,
I thought that general solution would be something like that, but
accounting for MAKEFLAGS in environment (because any of
prefix/execprefix/bindir may be overriden on command line), with
appropriate fallback if those heuristics doesn't work.
But now, I think that's just too messed, It would be easier to add
--bindir= option to libtool --mode=install and teach automake supply
it.
AO> --
AO> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135
