libtool: Invoking libtoolize
1
1 5.5.1 Invoking 'libtoolize'
1 ---------------------------
1
1 The 'libtoolize' program provides a standard way to add libtool support
1 to your package. In the future, it may implement better usage checking,
1 or other features to make libtool even easier to use.
1
1 The 'libtoolize' program has the following synopsis:
1
1 libtoolize [OPTION]...
1
1 and accepts the following options:
1
1 '--copy'
1 '-c'
1 Copy files from the libtool data directory rather than creating
1 symlinks.
1
1 '--debug'
1 Dump a trace of shell script execution to standard output. This
1 produces a lot of output, so you may wish to pipe it to 'less' (or
1 'more') or redirect to a file.
1
1 '--dry-run'
1 '-n'
1 Don't run any commands that modify the file system, just print them
1 out.
1
1 '--force'
1 '-f'
1 Replace existing libtool files. By default, 'libtoolize' won't
1 overwrite existing files.
1
1 '--help'
1 Display a help message and exit.
1
1 '--ltdl [TARGET-DIRECTORY-NAME]'
1 Install libltdl in the TARGET-DIRECTORY-NAME subdirectory of your
1 package. Normally, the directory is extracted from the argument to
1 'LT_CONFIG_LTDL_DIR' in 'configure.ac', though you can also specify
1 a subdirectory name here if you are not using Autoconf for example.
1 If 'libtoolize' can't determine the target directory, 'libltdl' is
1 used as the default.
1
1 '--no-warn'
1 Normally, Libtoolize tries to diagnose use of deprecated libtool
1 macros and other stylistic issues. If you are deliberately using
1 outdated calling conventions, this option prevents Libtoolize from
1 explaining how to update your project's Libtool conventions.
1
1 '--nonrecursive'
1 If passed in conjunction with '--ltdl', this option will cause the
1 'libltdl' installed by 'libtoolize' to be set up for use with a
1 non-recursive 'automake' build. To make use of it, you will need
1 to add the following to the 'Makefile.am' of the parent project:
1
1 ## libltdl/ltdl.mk appends to the following variables
1 ## so we set them here before including it:
1 BUILT_SOURCES =
1
1 AM_CPPFLAGS =
1 AM_LDFLAGS =
1
1 include_HEADERS =
1 noinst_LTLIBRARIES =
1 lib_LTLIBRARIES =
1 EXTRA_LTLIBRARIES =
1
1 EXTRA_DIST =
1
1 CLEANFILES =
1 MOSTLYCLEANFILES =
1
1 include libltdl/ltdl.mk
1
1 '--quiet'
1 '-q'
1 Work silently. 'libtoolize --quiet' is used by GNU Automake to add
1 libtool files to your package if necessary.
1
1 '--recursive'
1 If passed in conjunction with '--ltdl', this option will cause the
1 'libtoolize' installed 'libltdl' to be set up for use with a
1 recursive 'automake' build. To make use of it, you will need to
1 adjust the parent project's 'configure.ac':
1
1 AC_CONFIG_FILES([libltdl/Makefile])
1
1 and 'Makefile.am':
1
1 SUBDIRS += libltdl
1
1 '--subproject'
1 If passed in conjunction with '--ltdl', this option will cause the
1 'libtoolize' installed 'libltdl' to be set up for independent
1 configuration and compilation as a self-contained subproject. To
1 make use of it, you should arrange for your build to call
1 'libltdl/configure', and then run 'make' in the 'libltdl' directory
1 (or the subdirectory you put libltdl into). If your project uses
1 Autoconf, you can use the supplied 'LT_WITH_LTDL' macro, or else
1 call 'AC_CONFIG_SUBDIRS' directly.
1
1 Previous releases of 'libltdl' built exclusively in this mode, but
1 now it is the default mode both for backwards compatibility and
1 because, for example, it is suitable for use in projects that wish
1 to use 'libltdl', but not use the Autotools for their own build
1 process.
1
1 '--verbose'
1 '-v'
1 Work noisily! Give a blow by blow account of what 'libtoolize' is
1 doing.
1
1 '--version'
1 Print 'libtoolize' version information and exit.
1
1 Sometimes it can be useful to pass options to 'libtoolize' even
1 though it is called by another program, such as 'autoreconf'. A limited
1 number of options are parsed from the environment variable
1 'LIBTOOLIZE_OPTIONS': currently '--debug', '--no-warn', '--quiet' and
1 '--verbose'. Multiple options passed in 'LIBTOOLIZE_OPTIONS' must be
1 separated with a space, comma or a colon.
1
1 By default, a warning is issued for unknown options found in
1 'LIBTOOLIZE_OPTIONS' unless the first such option is '--no-warn'. Where
1 'libtoolize' has always quit on receipt of an unknown option at the
1 command line, this and all previous releases of 'libtoolize' will
1 continue unabated whatever the content of 'LIBTOOLIZE_OPTIONS' (modulo
1 some possible warning messages).
1
1 trick$ LIBTOOLIZE_OPTIONS=--no-warn,--quiet autoreconf --install
1
1 If 'libtoolize' detects an explicit call to 'AC_CONFIG_MACRO_DIRS'
1 (⇒The Autoconf Manual (autoconf)Input.) in your 'configure.ac', it
1 will put the Libtool macros in the specified directory.
1
1 In the future other Autotools will automatically check the contents
1 of 'AC_CONFIG_MACRO_DIRS', but at the moment it is more portable to add
1 the macro directory to 'ACLOCAL_AMFLAGS' in 'Makefile.am', which is
1 where the tools currently look. If 'libtoolize' doesn't see
1 'AC_CONFIG_MACRO_DIRS', it too will honour the first '-I' argument in
1 'ACLOCAL_AMFLAGS' when choosing a directory to store libtool
1 configuration macros in. It is perfectly sensible to use both
1 'AC_CONFIG_MACRO_DIRS' and 'ACLOCAL_AMFLAGS', as long as they are kept
1 in synchronisation.
1
1 ACLOCAL_AMFLAGS = -I m4
1
1 When you bootstrap your project with 'aclocal', then you will need to
1 explicitly pass the same macro directory with 'aclocal''s '-I' flag:
1
1 trick$ aclocal -I m4
1
1 If 'libtoolize' detects an explicit call to 'AC_CONFIG_AUX_DIR'
1 (⇒The Autoconf Manual (autoconf)Input.) in your 'configure.ac', it
1 will put the other support files in the specified directory. Otherwise
1 they too end up in the project root directory.
1
1 Unless '--no-warn' is passed, 'libtoolize' displays hints for adding
1 libtool support to your package, as well.
1