Remember that we need to add -lm to the link
command line because `foo.c' uses the cos(3) math library
function. See section Using libtool.
However, you should never use `-L' or `-l' flags to link against an uninstalled libtool library. Just specify the relative path to the `.la' file, such as `../intl/libintl.la'. This is a design decision to eliminate any ambiguity when linking against uninstalled shared libraries.
Don't accidentally strip the libraries, though, or they will be unusable.
AM_PROG_LIBTOOL
requires that you define the `Makefile' variable top_builddir in
your `Makefile.in'. Automake does this automatically, but Autoconf
users should set it to the relative path to the top of your build
directory (`../..', for example).
Unfortunately, as of libtool version 1.0, there is no way to specify inter-library dependencies on libtool libraries that have not yet been installed.
For static libraries, you could use a `-l' flag, but it would cause conflicts on systems which have non-PIC objects.
HP-UX, to be different, uses a function named
shl_load(3).
LIBPATH on AIX, and SHLIB_PATH on HP-UX.
Unfortunately, the DLD maintainer is also the libtool maintainer, so time spent on one of these projects takes time away from the other. When libtool is reasonably stable, DLD 4 development will proceed.
All code compiled for the PowerPC
and RS/6000 chips (powerpc-*-*, powerpcle-*-*, and
rs6000-*-*) is position-independent, regardless of the operating
system or compiler suite. So, "regular objects" can be used to build
shared libraries on these systems and no special PIC compiler flags are
required.
In the current implementation, libtool does not use any programs to strip libraries. Support will be added after it is clear how to write a portable test for library stripping programs.
This document was generated on 7 January 1998 using the texi2html translator version 1.51.