libtool: Invoking libtool
1
1 4 Invoking 'libtool'
1 ********************
1
1 The 'libtool' program has the following synopsis:
1
1 libtool [OPTION]... [MODE-ARG]...
1
1 and accepts the following options:
1
1 '--config'
1 Display libtool configuration variables and exit.
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 '-n'
1 '--dry-run'
1 Don't create, modify, or delete any files, just show what commands
1 would be executed by libtool.
1
1 '--features'
1 Display basic configuration options. This provides a way for
1 packages to determine whether shared or static libraries will be
1 built.
1
1 '--finish'
1 Same as '--mode=finish'.
1
1 '-h'
1 Display short help message.
1
1 '--help'
1 Display a help message and exit. If '--mode=MODE' is specified,
1 then detailed help for MODE is displayed.
1
1 '--help-all'
1 Display help for the general options as well as detailed help for
1 each operation mode, and exit.
1
1 '--mode=MODE'
1 Use MODE as the operation mode. When using libtool from the
1 command line, you can give just MODE (or a unique abbreviation of
1 it) as the first argument as a shorthand for the full
1 '--mode=MODE'. For example, the following are equivalent:
1
1 $ libtool --mode=execute --dry-run gdb prog.exe
1 $ libtool execute --dry-run gdb prog.exe
1 $ libtool exe --dry-run gdb prog.exe
1 $ libtool e --dry-run gdb prog.exe
1
1 MODE must be set to one of the following:
1
1 'compile'
1 Compile a source file into a libtool object.
1
1 'execute'
1 Automatically set the library path so that another program can
1 use uninstalled libtool-generated programs or libraries.
1
1 'link'
1 Create a library or an executable.
1
1 'install'
1 Install libraries or executables.
1
1 'finish'
1 Complete the installation of libtool libraries on the system.
1
1 'uninstall'
1 Delete installed libraries or executables.
1
1 'clean'
1 Delete uninstalled libraries or executables.
1
1 '--tag=TAG'
1 Use configuration variables from tag TAG (⇒Tags).
1
1 '--preserve-dup-deps'
1 Do not remove duplicate dependencies in libraries. When building
1 packages with static libraries, the libraries may depend circularly
1 on each other (shared libs can too, but for those it doesn't
1 matter), so there are situations, where -la -lb -la is required,
1 and the second -la may not be stripped or the link will fail. In
1 cases where these duplications are required, this option will
1 preserve them, only stripping the libraries that libtool knows it
1 can safely.
1
1 '--quiet'
1 '--silent'
1 Do not print out any progress or informational messages.
1
1 '-v'
1 '--verbose'
1 Print out progress and informational messages (enabled by default),
1 as well as additional messages not ordinary seen by default.
1
1 '--no-quiet'
1 '--no-silent'
1 Print out the progress and informational messages that are seen by
1 default. This option has no effect on whether the additional
1 messages seen in '--verbose' mode are shown.
1
1 '--no-verbose'
1 Do not print out any additional informational messages beyond those
1 ordinarily seen by default. This option has no effect on whether
1 the ordinary progress and informational messages enabled by
1 '--no-quiet' are shown.
1
1 Thus, there are now three different message levels (not counting
1 '--debug'), depending on whether the normal messages and/or the
1 additional verbose messages are displayed. Note that there is no
1 mechanism to display verbose messages, without also displaying
1 normal messages.
1
1 *default*
1 Normal messages are displayed, verbose messages are not
1 displayed. In addition to being the default mode, it can be
1 forcibly achieved by using both option '--no-verbose' and
1 either option '--no-silent' or option '--no-quiet'.
1
1 *silent*
1 Neither normal messages nor verbose messages are displayed.
1 This mode can be achieved using either option '--silent' or
1 option '--quiet'.
1
1 *verbose*
1 Both normal messages and verbose messages are displayed. This
1 mode can be achieved using either option '-v' or option
1 '--verbose'.
1
1 '--version'
1 Print libtool version information and exit.
1
1 The current 'libtool' implementation is done with a shell script that
1 needs to be invoked by the shell that 'configure' chose for configuring
1 'libtool' (⇒The Autoconf Manual (autoconf)config.status
1 Invocation.). This shell is set in the she-bang ('#!') line of the
1 'libtool' script. Using a different shell may cause undefined behavior.
1
1 The MODE-ARGS are a variable number of arguments, depending on the
1 selected operation mode. In general, each MODE-ARG is interpreted by
1 programs libtool invokes, rather than libtool itself.
1
Menu