If you don't
specify an rpath, then libtool builds a libtool convenience
archive, not a shared library (see section Linking static libraries).
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).
GNU Image Manipulation Program, for those who haven't taken the plunge. See http://www.gimp.org/.
Unfortunately, as of libtool version 1.3.3, there is no way to specify inter-library dependencies on libtool libraries that have not yet been installed. Libtool 1.4 will support this feature.
HP-UX,
to be different, uses a function named shl_load.
LIBPATH
on AIX, and SHLIB_PATH on HP-UX.
Even if libltdl is installed, `AC_LIBLTDL_INSTALLABLE' may fail to detect it, if libltdl depends on symbols provided by libraries other than the C library. In this case, it will needlessly build and install libltdl.
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.
This document was generated on 17 November 2000 using texi2html 1.56k.