Difference between revisions of "Configure"
From AMule Project FAQ
| Line 1: | Line 1: | ||
| − | + | ''configure'' configures [[aMule]] to adapt to many kinds of systems. | |
| − | + | ||
| − | + | It's usage is ''./configure [OPTION]... [VAR=VALUE]...'' | |
| − | + | ''VAR=VALUE'' stands for environment variables you want to specify (''VAR'' is the variable name and ''VALUE'' its value, obviously). For example, ''CC=gcc'' or ''CFLAGS="-O2''. | |
| − | + | ||
| − | + | ''OPTION'' is any (or several) of the options described bellow: | |
| − | + | {| border=1 | |
| − | + | |''-h'' or ''--help'' || This will display a help message summing up all ''configure'' options | |
| − | + | |- | |
| − | + | |''-V'' or ''--version'' || This will display the version information | |
| − | + | |- | |
| − | + | |''-q'' or ''--quiet'' or ''--silent'' || Do not print the `checking...' messages, only the final summed up ouput | |
| − | + | |- | |
| − | + | |''--cache-file=FILE || Store the checkings' ouputs in ''FILE'' in a script format, so you can reuse without the need to rerun ''configure'' (read the cached file for more information) | |
| − | + | |- | |
| − | + | |''-C'' or ''--config-cache || Same as ''--cache-file=config.cache'' | |
| + | |- | ||
| + | |''-n'' or ''--no-create || Just run configure, but do not create any file | ||
| + | |- | ||
| + | |''--srcdir=DIR'' || Look for the sources in ''DIR'' [configure dir or `..'] | ||
| + | |} | ||
| + | |||
| + | <pre> | ||
Installation directories: | Installation directories: | ||
Revision as of 23:35, 27 March 2005
configure configures aMule to adapt to many kinds of systems.
It's usage is ./configure [OPTION]... [VAR=VALUE]...
VAR=VALUE stands for environment variables you want to specify (VAR is the variable name and VALUE its value, obviously). For example, CC=gcc or CFLAGS="-O2.
OPTION is any (or several) of the options described bellow:
| -h or --help | This will display a help message summing up all configure options |
| -V or --version | This will display the version information |
| -q or --quiet or --silent | Do not print the `checking...' messages, only the final summed up ouput |
| --cache-file=FILE | Store the checkings' ouputs in FILE in a script format, so you can reuse without the need to rerun configure (read the cached file for more information) |
| -C or --config-cache | Same as --cache-file=config.cache |
| -n or --no-create | Just run configure, but do not create any file |
| --srcdir=DIR | Look for the sources in DIR [configure dir or `..'] |
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[/usr/local]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]
By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc. You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.
For better control, use the options below.
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--datadir=DIR read-only architecture-independent data [PREFIX/share]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--infodir=DIR info documentation [PREFIX/info]
--mandir=DIR man documentation [PREFIX/man]
Program names:
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names
X features:
--x-includes=DIR X include files are in DIR
--x-libraries=DIR X library files are in DIR
System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
--target=TARGET configure for building compilers for TARGET [HOST]
Optional Features:
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-maintainer-mode enable make rules and dependencies not useful
(and sometimes confusing) to the casual installer
--disable-dependency-tracking speeds up one-time build
--enable-dependency-tracking do not reject slow dependency extractors
--enable-debug enable additional debugging output
--disable-debug disable additional debugging output
--enable-optimize enable code optimizing
--enable-optimise enable code optimizing (deprecated)
--enable-profile enable code profiling
--enable-static produce a statically linked executable
--enable-embedded_crypto use embedded Crypto code (default)
--enable-amulecmd compile aMule command line client
--enable-amulecmdgui compile aMule command line client (GUI version)
--enable-amule-gui compile aMule remote GUI (EXPERIMENTAL)
--enable-amule-daemon compile aMule daemon version
--enable-webserver compile aMule WebServer
--enable-webservergui compile aMule WebServer GUI
--enable-cas compile C aMule Statistics
--enable-wxcas compile aMule GUI Statistics
--disable-ed2k don't compile aMule ed2k links handler
--enable-alc compile aMuleLinkCreator GUI version
--enable-alcc compile aMuleLinkCreator for console
--disable-gsocket disable gsocket.c linking
--disable-gtk disable pure GTK code in amule
--enable-utf8-systray use UTF-8 encoded strings in the systray
--disable-systray disable SysTray compilation
--disable-monolithic disable building of the monolithic aMule app
--disable-gtktest do not try to compile and run a test GTK+ program
--disable-gtktest do not try to compile and run a test GTK program
--disable-rpath do not hardcode runtime library paths
--disable-nls do not use Native Language Support
--enable-ccache enable ccache support for fast recompilation
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-zlib=PREFIX use zlib in PREFIX
--with-curl-config=CONFIG curl-config script to use (optional)
--with-curl-prefix=PREFIX prefix where curl is installed (optional) (un
used)
--with-gdlib-prefix=PREFIX prefix where gdlib is installed (optional)
--with-gdlib-exec-prefix=PREFIX exec prefix where gdlib is installed (option
al)
--with-gdlib-config=CONFIG gdlib-config script to use (optional)
--with-libpng-prefix=PREFIX prefix where libpng is installed
--with-libpng-exec-prefix=PREFIX exec prefix where libpng is installed
--with-libpng-config=CONFIG libpng-config script to use
--with-wx-prefix=PREFIX prefix where wxWidgets is installed (optional
)
--with-wx-exec-prefix=PREFIX exec prefix where wxWidgets is installed (opt
ional)
--with-wx-config=CONFIG wx-config script to use (optional)
--with-wxbase-prefix=PREFIX prefix where wxWidgets base is installed (opt
ional)
--with-wxbase-exec-prefix=PREFIX exec prefix where wxWidgetsbase is installed
(optional)
--with-wxbase-config=CONFIG wxbase-config script to use (optional)
--with-gtk-prefix=PREFIX prefix where GTK is installed (optional)
--with-gtk-exec-prefix=PREFIX exec prefix where GTK is installed (optional)
--with-crypto-prefix=PREFIX prefix where crypto++ is installed (optional)
--with-x use the X Window System
--with-gnu-ld assume the C compiler uses GNU ld default=no
--with-libiconv-prefix=DIR search for libiconv in DIR/include and DIR/lib
--without-libiconv-prefix don't search for libiconv in includedir and libd
ir
--with-included-gettext use the GNU gettext library included here
--with-libintl-prefix=DIR search for libintl in DIR/include and DIR/lib
--without-libintl-prefix don't search for libintl in includedir and libdir
--with-ccache-prefix=PREFIX prefix where ccache is installed (optional)
Some influential environment variables:
CXX C++ compiler command
CXXFLAGS C++ compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
headers in a nonstandard directory <include dir>
CXXCPP C++ preprocessor
CC C compiler command
CFLAGS C compiler flags
CPP C preprocessor
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
Report bugs to deltahf@amule.org.