Go to the first, previous, next, last section, table of contents.


Invoking ltconfig

ltconfig runs a series of configuration tests, then creates a system-specific libtool in the current directory. The ltconfig program has the following synopsis:

ltconfig [option]... ltmain [host]

and accepts the following options:

`--disable-shared'
Create a libtool that only builds static libraries.
`--disable-static'
Create a libtool that builds only shared libraries if they are available. If only static libraries can be built, then this flag has no effect.
`--help'
Display a help message and exit.
`--no-verify'
Do not use config.sub to verify that host is a valid canonical host system name.
`--quiet'
`--silent'
Do not print informational messages when running configuration tests.
`--srcdir=dir'
Look for config.guess and config.sub in dir.
`--version'
Print ltconfig version information and exit.
`--with-gcc'
Assume that the GNU C compiler will be used when invoking the created libtool to compile and link object files.

ltmain is the ltmain.sh shell script fragment that provides the basic libtool functionality (see section Including libtool with your package).

host is the canonical host system name, which by default is guessed by running config.guess.

ltconfig also recognizes the following environment variables:

Variable: CC
The C compiler that will be used by the generated libtool.

Variable: CFLAGS
Compiler flags used to generate standard object files.

Variable: CPPFLAGS
C preprocessor flags.

Variable: LD
The system linker to use (if the generated libtool requires one).

Variable: RANLIB
Program to use rather than checking for ranlib.


Go to the first, previous, next, last section, table of contents.