GNU Libtool

For version 1.2a, 19 April 1998

Gordon Matzigkeit


(1)

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.

(2)

Don't accidentally strip the libraries, though, or they will be unusable.

(3)

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).

(4)

GNU Image Manipulation Program, for those who haven't taken the plunge. See http://www.gimp.org/.

(5)

Unfortunately, as of libtool version 1.2a, there is no way to specify inter-library dependencies on libtool libraries that have not yet been installed.

(6)

HP-UX, to be different, uses a function named shl_load(3).

(7)

LIBPATH on AIX, and SHLIB_PATH on HP-UX.

(8)

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.

(9)

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 24 May 1999 using texi2html 1.55k.