| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This chapter describes how to integrate libtool with your packages so that your users can install hassle-free shared libraries.
| 5.1 Autoconf macros exported by libtool | ||
| 5.2 Writing `Makefile' rules for libtool | ||
| 5.3 Using Automake with libtool | Automatically supporting libtool. | |
| 5.4 Configuring libtool | Configuring libtool for a host system. | |
| 5.5 Including libtool in your package | What files to distribute with your package. | |
| 5.6 Static-only libraries | Sometimes shared libraries are just a pain. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Libtool uses a number of macros to interrogate the host system when it is being built, and you can use some of them yourself too. Although there are a great many other macros in the libtool installed m4 files, these do not form part of the published interface, and are subject to change between releases.
Macros in the `LT_CMD_' namespace check for various shell commands:
Finds the longest command line that can be safely passed to `$SHELL' without being truncated, and store in the shell variable `$max_cmd_len'. It is only an approximate value, but command lines of this length or shorter are guaranteed not to be truncated.
Macros in the `LT_FUNC_' namespace check characteristics of library functions:
`AC_DEFINE' the preprocessor symbol `DLSYM_USCORE' if we have to add an underscore to symbol-names passed in to `dlsym'.
Macros in the `LT_LIB_' namespace check characteristics of system libraries:
Set `LIBM' to the math library or libraries required on this machine, if any.
This is the macro used by `libltdl' to determine which dlloaders to use on this machine, if any. Several shell variables are set (and `AC_SUBST'ed) depending on the dlload interfaces are available on this machine. `LT_DLLOADERS' contains a list of libtool libraries that can be used, and if necessary also sets `LIBADD_DLOPEN' if additional system libraries are required by the `dlopen' loader, and `LIBADD_SHL_LOAD' if additional system libraries are required by the `shl_load' loader, respectively. Finally some symbols are set in `config.h' depending on the loaders that are found to work: `HAVE_LIBDL', `HAVE_SHL_LOAD', `HAVE_DYLD', `HAVE_DLD'.
Macros in the `LT_PATH_' namespace search the system for the full path to particular system commands:
Add a `--with-gnu-ld' option to `configure'. Try to find
the path to the linker used by `$CC', and whether it is the
GNU linker. The result is stored in the shell variable
`$LD', which is AC_SUBSTed.
Try to find a BSD compatible nm or a MS compatible
dumpbin command on this machine. The result is stored in the
shell variable `$NM', which is AC_SUBSTed.
Macros in the `LT_SYS_' namespace probe for system characteristics:
Tests whether a program can dlopen itself, and then also whether the same program can still dlopen itself when statically linked. Results are stored in the shell variables `$enable_dlopen_self' and `enable_dlopen_self_static' respectively.
Define the preprocessor symbol `LTDL_DLOPEN_DEPLIBS' if the OS needs help to load dependent libraries for `dlopen' (or equivalent).
Define the preprocessor symbol `LT_DLSEARCH_PATH' to the system default library search path.
Define the preprocessor symbol `LT_MODULE_EXT' to the extension used for runtime loadable modules. If you use libltdl to open modules, then you can simply use the libtool library extension, `.la'.
Define the preprocessor symbol `LT_MODULE_PATH_VAR' to the name of the shell environment variable that determines the run-time module search path.
Set the shell variable `sys_symbol_underscore' to `no' unless the compiler prefixes global symbols with an underscore.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Libtool is fully integrated with Automake (see (automake)Top section `Introduction' in The Automake Manual), starting with Automake version 1.2.
If you want to use libtool in a regular `Makefile' (or `Makefile.in'), you are on your own. If you're not using Automake, and you don't know how to incorporate libtool into your package you need to do one of the following:
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Libtool library support is implemented under the `LTLIBRARIES' primary.
Here are some samples from the Automake `Makefile.am' in the libtool distribution's `demo' subdirectory.
First, to link a program against a libtool library, just use the `program_LDADD'(5) variable:
bin_PROGRAMS = hell hell_static # Build hell from main.c and libhello.la hell_SOURCES = main.c hell_LDADD = libhello.la # Create a statically linked version of hell. hell_static_SOURCES = main.c hell_static_LDADD = libhello.la hell_static_LDFLAGS = -static |
You may use the `program_LDFLAGS' variable to stuff in any flags you want to pass to libtool while linking `program' (such as `-static' to avoid linking uninstalled shared libtool libraries).
Building a libtool library is almost as trivial… note the use of `libhello_la_LDFLAGS' to pass the `-version-info' (see section Library interface versions) option to libtool:
# Build a libtool library, libhello.la for installation in libdir. lib_LTLIBRARIES = libhello.la libhello_la_SOURCES = hello.c foo.c libhello_la_LDFLAGS = -version-info 3:12:1 |
The `-rpath' option is passed automatically by Automake (except for
libraries listed as noinst_LTLIBRARIES), so you
should not specify it.
See Building a Shared Library: (automake)A Shared Library section `The Automake Manual' in The Automake Manual, for more information.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Libtool requires intimate knowledge of your compiler suite and operating system in order to be able to create shared libraries and link against them properly. When you install the libtool distribution, a system-specific libtool script is installed into your binary directory.
However, when you distribute libtool with your own packages (see section Including libtool in your package), you do not always know the compiler suite and operating system that are used to compile your package.
For this reason, libtool must be configured before it can be
used. This idea should be familiar to anybody who has used a GNU
configure script. configure runs a number of tests for
system features, then generates the `Makefile's (and possibly a
`config.h' header file), after which you can run make and
build the package.
Libtool adds its own tests to your configure script in order to
generate a libtool script for the installer's host machine.
5.4.1 The LT_INIT macro | Configuring libtool in `configure.ac'.
| |
| 5.4.2 Platform-specific configuration notes | Platform-specific notes for configuration. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
LT_INIT macro If you are using GNU Autoconf (or Automake), you should add a call to
LT_INIT to your `configure.ac' file. This macro
adds many new tests to the configure script so that the generated
libtool script will understand the characteristics of the host. It's the
most important of a number of macros defined by Libtool:
Ensure that a recent enough version of Libtool is being used. If the
version of Libtool used for LT_INIT is earlier than
version, print an error message to the standard
error output and exit with failure (exit status is 63). For example:
LT_PREREQ([2.2.6]) |
Add support for the `--enable-shared' and `--disable-shared'
configure flags.(6) AC_PROG_LIBTOOL and
AM_PROG_LIBTOOL are deprecated names for older versions of this macro;
autoupdate will upgrade your `configure.ac' files.
By default, this macro turns on shared libraries if they are available,
and also enables static libraries if they don't conflict with the shared
libraries. You can modify these defaults by passing either
disable-shared or disable-static in the option list to
LT_INIT, or using AC_DISABLE_SHARED or AC_DISABLE_STATIC.
# Turn off shared libraries during beta-testing, since they # make the build process take too long. LT_INIT([disable-shared]) |
The user may specify modified forms of the configure flags
`--enable-shared' and `--enable-static' to choose whether
shared or static libraries are built based on the name of the package.
For example, to have shared `bfd' and `gdb' libraries built,
but not shared `libg++', you can run all three configure
scripts as follows:
trick$ ./configure --enable-shared=bfd,gdb |
In general, specifying `--enable-shared=pkgs' is the same as configuring with `--enable-shared' every package named in the comma-separated pkgs list, and every other package with `--disable-shared'. The `--enable-static=pkgs' flag behaves similarly, but it uses `--enable-static' and `--disable-static'. The same applies to the `--enable-fast-install=pkgs' flag, which uses `--enable-fast-install' and `--disable-fast-install'.
The package name `default' matches any packages that have not set
their name in the PACKAGE environment variable.
This macro also sets the shell variable LIBTOOL_DEPS, that you can use to automatically update the libtool script if it becomes out-of-date. In order to do that, add to your `configure.ac':
LT_INIT AC_SUBST([LIBTOOL_DEPS]) |
and, to `Makefile.in' or `Makefile.am':
LIBTOOL_DEPS = @LIBTOOL_DEPS@
libtool: $(LIBTOOL_DEPS)
$(SHELL) ./config.status --recheck
|
If you are using GNU Automake, you can omit the assignment, as Automake will take care of it. You'll obviously have to create some dependency on `libtool'.
Aside from disable-static and disable-shared, there are
other options that you can pass to LT_INIT to modify its
behaviour. Here is a full list:
Enable checking for dlopen support. This option should be used if the package makes use of the `-dlopen' and `-dlpreopen' libtool flags, otherwise libtool will assume that the system does not support dlopening.
This option should be used if the package has been ported to build clean
dlls on win32 platforms. Usually this means that any library data items
are exported with __declspec(dllexport) and imported with
__declspec(dllimport). If this macro is not used, libtool will
assume that the package libraries are not dll clean and will build only
static libraries on win32 hosts.
Provision must be made to pass `-no-undefined' to libtool
in link mode from the package Makefile. Naturally, if you pass
`-no-undefined', you must ensure that all the library symbols
really are defined at link time!
Change the default behaviour for LT_INIT to disable
optimization for fast installation. The user may still override this
default, depending on platform support, by specifying
`--enable-fast-install' to configure.
Change the default behaviour for LT_INIT to enable
shared libraries. This is the default on all systems where
Libtool knows how to create shared libraries.
The user may still override this default by specifying
`--disable-shared' to configure.
Change the default behaviour for LT_INIT to disable
shared libraries. The user may still override this default by
specifying `--enable-shared' to configure.
Change the default behaviour for LT_INIT to enable
static libraries. This is the default on all systems where
shared libraries have been disabled for some reason, and on
most systems where shared libraries have been enabled.
If shared libraries are enabled, the user may still override
this default by specifying `--disable-static' to
configure.
Change the default behaviour for LT_INIT to disable
static libraries. The user may still override this default by
specifying `--enable-static' to configure.
Change the default behaviour for libtool to try to use only
PIC objects. The user may still override this default by specifying
`--without-pic' to configure.
Change the default behaviour of libtool to try to use only
non-PIC objects. The user may still override this default by
specifying `--with-pic' to configure.
Enable libtool support for the language given if it
has not yet already been enabled. Languages accepted are "C++",
"Fortran 77", "Java" and "Windows Resource".
If Autoconf language support macros such as AC_PROG_CXX are
used in your `configure.ac', Libtool language support will automatically
be enabled.
Conversely using LT_LANG to enable language support for Libtool
will automatically enable Autoconf language support as well.
Both of the following examples are therefore valid ways of adding C++ language support to Libtool.
LT_INIT LT_LANG([C++]) |
LT_INIT AC_PROG_CXX |
This macro is deprecated, the `dlopen' option to LT_INIT should be
used instead.
This macro is deprecated, the `win32-dll' option to LT_INIT should
be used instead.
This macro is deprecated, the `disable-fast-install' option to LT_INIT
should be used instead.
Change the default behaviour for LT_INIT to disable shared libraries.
The user may still override this default by specifying `--enable-shared'.
The option `disable-shared' to LT_INIT is a shorthand for this.
AM_DISABLE_SHARED is a deprecated alias for AC_DISABLE_SHARED.
Change the default behaviour for LT_INIT to enable shared libraries.
This is the default on all systems where Libtool knows how to create
shared libraries. The user may still override this default by specifying
`--disable-shared'. The option `shared' to LT_INIT is a
shorthand for this.
AM_ENABLE_SHARED is a deprecated alias for AC_ENABLE_SHARED.
Change the default behaviour for LT_INIT to disable static libraries.
The user may still override this default by specifying `--enable-static'.
The option `disable-static' to LT_INIT is a shorthand for this.
AM_DISABLE_STATIC is a deprecated alias for AC_DISABLE_STATIC.
Change the default behaviour for LT_INIT to enable static libraries.
This is the default on all systems where shared libraries have been disabled
for some reason, and on most systems where shared libraries have been enabled.
If shared libraries are enabled, the user may still override this default by
specifying `--disable-static'. The option `static' to LT_INIT
is a shorthand for this.
AM_ENABLE_STATIC is a deprecated alias for AC_ENABLE_STATIC.
The tests in LT_INIT also recognize the following
environment variables:
The C compiler that will be used by the generated libtool. If
this is not set, LT_INIT will look for gcc or
cc.
Compiler flags used to generate standard object files. If this is not
set, LT_INIT will not use any such flags. It affects
only the way LT_INIT runs tests, not the produced
libtool.
C preprocessor flags. If this is not set, LT_INIT will
not use any such flags. It affects only the way LT_INIT
runs tests, not the produced libtool.
The system linker to use (if the generated libtool requires one).
If this is not set, LT_INIT will try to find out what is
the linker used by CC.
The flags to be used by libtool when it links a program. If
this is not set, LT_INIT will not use any such flags. It
affects only the way LT_INIT runs tests, not the produced
libtool.
The libraries to be used by LT_INIT when it links a
program. If this is not set, LT_INIT will not use any
such flags. It affects only the way LT_INIT runs tests,
not the produced libtool.
Program to use rather than checking for nm.
Program to use rather than checking for ranlib.
A command that creates a link of a program, a soft-link if possible, a
hard-link otherwise. LT_INIT will check for a suitable
program if this variable is not set.
Program to use rather than checking for dlltool. Only meaningful
for Cygwin/MS-Windows.
Program to use rather than checking for objdump. Only meaningful
for Cygwin/MS-Windows.
Program to use rather than checking for as. Only used on
Cygwin/MS-Windows at the moment.
With 1.3 era libtool, if you wanted to know any details of what
libtool had discovered about your architecture and environment, you
had to run the script with `--config' and grep through the
results. This idiom was supported up to and including 1.5.x era
libtool, where it was possible to call the generated libtool script
from `configure.ac' as soon as LT_INIT had
completed. However, one of the features of libtool 1.4 was that the
libtool configuration was migrated out of a separate `ltconfig'
file, and added to the LT_INIT macro (nee AC_PROG_LIBTOOL),
so the results of the configuration tests were available directly to code in
`configure.ac', rendering the call out to the generated libtool
script obsolete.
Starting with libtool 2.0, the multipass generation of the libtool script has been consolidated into a single `config.status' pass, which happens after all the code in `configure.ac' has completed. The implication of this is that the libtool script does not exist during execution of code from `configure.ac', and so obviously it cannot be called for `--config' details anymore. If you are upgrading projects that used this idiom to libtool 2.0 or newer, you should replace those calls with direct references to the equivalent Autoconf shell variables that are set by the configure time tests before being passed to `config.status' for inclusion in the generated libtool script.
By default, the configured `libtool' script is generated by the
call to AC_OUTPUT command, and there is rarely any need to use
`libtool' from `configure'. However, sometimes it is
necessary to run configure time compile and link tests using
`libtool'. You can add LT_OUTPUT to your
`configure.ac' any time after LT_INIT and any
LT_LANG calls; that done, `libtool' will be created by a
specially generated `config.lt' file, and available for use in
later tests.
Also, when LT_OUTPUT is used, for backwards compatibility with
Automake regeneration rules, `config.status' will call
`config.lt' to regenerate `libtool', rather than generating
the file itself.
When you invoke the libtoolize program (see section Invoking libtoolize), it will tell you where to find a definition of
LT_INIT. If you use Automake, the aclocal program
will automatically add LT_INIT support to your
`configure' script when it sees the invocation of LT_INIT
in `configure.ac'.
Because of these changes, and the runtime version compatibility checks
Libtool now executes, we now advise against including a copy of
`libtool.m4' (and brethren) in `acinclude.m4'. Instead,
you should set your project macro directory with
AC_CONFIG_MACRO_DIR. When you libtoolize your
project, a copy of the relevant macro definitions will be placed in
your AC_CONFIG_MACRO_DIR, where aclocal can reference
them directly from `aclocal.m4'.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
While Libtool tries to hide as many platform-specific features as possible, some have to be taken into account when configuring either the Libtool package or a libtoolized package.
LDFLAGS=-Wl,-brtl for the latter style.
AR=/usr/bin/ar LD=/usr/bin/ld NM='/usr/bin/nm -B'.
/bin/sh is very slow due to its inefficient handling
of here-documents. A modern shell is preferable:
CONFIG_SHELL=/bin/bash; export $CONFIG_SHELL $CONFIG_SHELL ./configure [...] |
CXX='pgCC --one_instantiation_per_object' and avoid parallel make.
MACOSX_DEPLOYMENT_TARGET is set to
10.3 or later at configure time. See rdar://problem/4135857
for more information on this issue.
sed programs are horribly broken, and cannot handle
libtool's requirements, so users may report unusual problems. There
is no workaround except to install a working sed (such as GNU sed)
on these systems.
cc programs emits copyright
on standard error that confuse tests on size of `conftest.err'. The
workaround is to specify CC when run configure with
CC='cc -Hnocopyr'.
gcc provided by Marco Walther.
libtool sometimes guesses the wrong paths that the linker
and dynamic linker search by default. If this occurs, you may override
libtool's guesses at configure time by setting the
autoconf cache variables
lt_cv_sys_lib_search_path_spec and
lt_cv_sys_lib_dlsearch_path_spec respectively to the correct search
paths.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In order to use libtool, you need to include the following files with your package:
Attempt to guess a canonical system name.
Canonical system name validation subroutine script.
BSD-compatible install replacement script.
A generic script implementing basic libtool functionality.
Note that the libtool script itself should not be included with your package. See section Configuring libtool.
You should use the libtoolize program, rather than manually
copying these files into your package.
5.5.1 Invoking libtoolize | libtoolize command line options.
| |
5.5.2 Autoconf and LTLIBOBJS | Autoconf automates LTLIBOBJS generation. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
libtoolize The libtoolize program provides a standard way to add libtool
support to your package. In the future, it may implement better usage
checking, or other features to make libtool even easier to use.
The libtoolize program has the following synopsis:
libtoolize [option]… |
and accepts the following options:
Copy files from the libtool data directory rather than creating symlinks.
Dump a trace of shell script execution to standard output. This
produces a lot of output, so you may wish to pipe it to less (or
more) or redirect to a file.
Don't run any commands that modify the file system, just print them out.
Replace existing libtool files. By default, libtoolize won't
overwrite existing files.
Display a help message and exit.
Install libltdl in the TARGET-DIRECTORY-NAME subdirectory of
your package. Normally, the directory is extracted from the argument
to LT_CONFIG_LTDL_DIR in `configure.ac', though you can
also specify a subdirectory name here if you are not using Autoconf
for example. If libtoolize can't determine the target
directory, `libltdl' is used as the default.
Normally, Libtoolize tries to diagnose use of deprecated libtool macros and other stylistic issues. If you are deliberately using outdated calling conventions, this option prevents Libtoolize from explaining how to update your project's Libtool conventions.
If passed in conjunction with `--ltdl', this option will cause
the libltdl installed by `libtoolize' to be set up for
use with a non-recursive automake build. To make use of it,
you will need to add the following to the `Makefile.am' of the
parent project:
## libltdl/Makefile.inc appends to the following variables ## so we set them here before including it: BUILT_SOURCES = AM_CPPFLAGS = AM_LDFLAGS = include_HEADERS = noinst_LTLIBRARIES = lib_LTLIBRARIES = EXTRA_LTLIBRARIES = EXTRA_DIST = CLEANFILES = MOSTLYCLEANFILES = include libltdl/Makefile.inc |
Work silently. `libtoolize --quiet' is used by GNU Automake to add libtool files to your package if necessary.
If passed in conjunction with `--ltdl', this option will cause
the libtoolize installed `libltdl' to be set up for use
with a recursive automake build. To make use of it, you
will need to adjust the parent project's `configure.ac':
AC_CONFIG_FILES([libltdl/Makefile]) |
and `Makefile.am':
SUBDIRS += libltdl |
If passed in conjunction with `--ltdl', this option will cause
the libtoolize installed `libltdl' to be set up for
independent configuration and compilation as a self-contained
subproject. To make use of it, you should arrange for your build to
call libltdl/configure, and then run make in the
`libltdl' directory (or the subdirectory you put libltdl into).
If your project uses Autoconf, you can use the supplied
`LT_WITH_LTDL' macro, or else call `AC_CONFIG_SUBDIRS'
directly.
Previous releases of `libltdl' built exclusively in this mode, but now it is the default mode both for backwards compatibility and because, for example, it is suitable for use in projects that wish to use `libltdl', but not use the Autotools for their own build process.
Work noisily! Give a blow by blow account of what
libtoolize is doing.
Print libtoolize version information and exit.
Sometimes it can be useful to pass options to libtoolize even
though it is called by another program, such as autoreconf. A
limited number of options are parsed from the environment variable
LIBTOOLIZE_OPTIONS: currently `--debug', `--no-warn',
`--quiet' and `--verbose'. Multiple options passed in
LIBTOOLIZE_OPTIONS must be separated with a space, comma or a
colon.
By default, a warning is issued for unknown options found in
LIBTOOLIZE_OPTIONS unless the first such option is
`--no-warn'. Where libtoolize has always quit
on receipt of an unknown option at the command line, this and all
previous releases of libtoolize will continue unabated whatever
the content of LIBTOOLIZE_OPTIONS (modulo some possible warning
messages).
trick$ LIBTOOLIZE_OPTIONS=--no-warn,--quiet autoreconf --install |
If libtoolize detects an explicit call to
AC_CONFIG_MACRO_DIR (see (autoconf)Input section `The Autoconf Manual' in The Autoconf Manual) in your `configure.ac', it will
put the Libtool macros in the specified directory.
In the future other Autotools will automatically check the contents of
AC_CONFIG_MACRO_DIR, but at the moment it is more portable to
add the macro directory to ACLOCAL_AMFLAGS in
`Makefile.am', which is where the tools currently look. If
libtoolize doesn't see AC_CONFIG_MACRO_DIR, it too
will honour the first `-I' argument in ACLOCAL_AMFLAGS
when choosing a directory to store libtool configuration macros in.
It is perfectly sensible to use both AC_CONFIG_MACRO_DIR and
ACLOCAL_AMFLAGS, as long as they are kept in synchronisation.
ACLOCAL_AMFLAGS = -I m4 |
When you bootstrap your project with aclocal, then you will
need to explicitly pass the same macro directory with
aclocal's `-I' flag:
trick$ aclocal -I m4 |
If libtoolize detects an explicit call to
AC_CONFIG_AUX_DIR (see (autoconf)Input section `The Autoconf Manual' in The Autoconf Manual) in your `configure.ac', it
will put the other support files in the specified directory.
Otherwise they too end up in the project root directory.
Unless `--no-warn' is passed, libtoolize displays
hints for adding libtool support to your package, as well.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
LTLIBOBJS People used to add code like the following to their `configure.ac':
LTLIBOBJS=`echo "$LIBOBJS" | sed 's/\.[^.]* /.lo /g;s/\.[^.]*$/.lo/'` AC_SUBST([LTLIBOBJS]) |
This is no longer required (since Autoconf 2.54), and doesn't take Automake's deansification support into account either, so doesn't work correctly even with ancient Autoconfs!
Provided you are using a recent (2.54 or better) incarnation of
Autoconf, the call to AC_OUTPUT takes care of setting
LTLIBOBJS up correctly, so you can simply delete such snippets
from your `configure.ac' if you had them.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When you are developing a package, it is often worthwhile to configure
your package with the `--disable-shared' flag, or to override the
defaults for LT_INIT by using the disable-shared option
(see section The LT_INIT macro). This prevents libtool
from building shared libraries, which has several advantages:
You may want to put a small note in your package `README' to let other developers know that `--disable-shared' can save them time. The following example note is taken from the GIMP(7) distribution `README':
The GIMP uses GNU Libtool in order to build shared libraries on a variety of systems. While this is very nice for making usable binaries, it can be a pain when trying to debug a program. For that reason, compilation of shared libraries can be turned off by specifying the `--disable-shared' option to `configure'. |
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated on July, 20 2009 using texi2html 1.76.