Buy GNU books!
|[Top]||[Contents]||[Index]||[ ? ]|
If you don't
rpath, then libtool builds a libtool convenience
archive, not a shared library (see section 3.7 Linking static libraries).
However, you should avoid using `-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.
AC_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/.
We used to recommend
__END_DECLS. This was bad advice since
symbols (even preprocessor macro names) that begin with an underscore
are reserved for the use of the compiler.
to be different, uses a function named
on AIX, and
SHLIB_PATH on HP-UX.
This is used for
the host dependent module loading API --
LoadLibrary for example
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 (
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
|webmaster donations bookstore||delorie software privacy|
|Copyright © 2003 by The Free Software Foundation||Updated Jun 2003|