| www.delorie.com/gnu/docs/fontutils/fontu_3.html | search |
 Buy GNU books! | |
| www.delorie.com/gnu/docs/fontutils/fontu_3.html | search |
|
Buy GNU books! | |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
configure script
(This section is largely from the Autoconf manual, by David MacKenzie.
See section `Running configure scripts' in Autoconf.)
The configure script that comes with the font utilities is
generated automatically by the Autoconf program. You can regenerate
configure by rerunning Autoconf (for example, if a new version of
Autoconf is released); you must arrange for Autoconf to use the macros
in `./aclocal.m4' (see section `Generating configure' in Autoconf).
The purpose of configure is to adapt the source code to your
system: for example, the name of the directory header file
(`dirent.h' or `sys/dir.h'), whether an install program
is available, and so on.
Normally, you do not need to give any options to configure; you
cd to the directory with the source code and type
`configure'. Exceptions: if `.' is not in your PATH,
you must type `./configure'; if you are using a
non-Bourne-compatible shell on some old systems, you must samp `sh
configure'.
Running configure takes a minute or two. While it is running, it
prints some messages that tell what it is doing. If you don't want to
see the messages, run configure with its standard output
redirected to `/dev/null'; for example, `configure >/dev/null'.
To compile the package in a different directory from the one containing
the source code, you must use a variant of Make that supports the
VPATH variable, such as GNU Make. cd to the
directory where you want the object files and executables to go and run
configure with the option `--srcdir=dir', where
dir is the directory that contains the source code. Using this
option is unnecessary if the source code is in the parent directory of
the one in which you are compiling; configure automatically
checks for the source code in `..' if it does not find it in
`.'.
configure guesses the default installation prefix (we'll call it
$(prefix)) by looking for the directory which contains the
command gcc, and using its parent. For example, if gcc is
installed as `/usr/local/gnu/bin/gcc', $(prefix) will be set
to `/usr/local/gnu'.
You can override this default guess for the installation prefix by giving
configure the option `--prefix=path'. You can also
specify separate installation prefixes for architecture-specific files
and architecture-independent files by giving configure the option
`--exec_prefix=xpath'. Then xpath will be the prefix
for installing programs and libraries. Data files and documentation
will still use the regular prefix. Normally, all files are installed
using the regular prefix.
You can tell configure to figure out the configuration for your
system, and record it in `config.status', without actually
configuring the package. To do this, give configure the
`--no-create' option. Later, you can run `./config.status' to
actually configure the package. This option is useful mainly in
`Makefile' rules for updating `config.status' and the
`Makefile' itself. You can also give `config.status' the
`--recheck' option, which makes it rerun configure with the
same arguments you used before. This is useful if you change
configure.
configure ignores any other arguments that you give it.
On systems that require unusual options for compilation or linking that
the package's configure script does not know about, you can give
configure initial values for variables by setting them in the
environment. In Bourne-compatible shells, you can do that on the
command line like this:
CC='gcc -traditional' LIBS=-lposix sh configure |
The Make variables that you might want to override with
environment variables when running configure are:
(For these variables, any value given in the environment overrides the
value that configure would choose.)
CC
gcc if that is in your
PATH, cc otherwise.
INSTALL
install if you
have it, cp otherwise.
(For these variables, any value given in the environment is added to
the value that configure chooses.)
DEFS
AC_CONFIG_HEADER (including the file
utilities) do not use this variable.
LIBS
Of course, problems requiring manual intervention (e.g., setting these variables) should ideally be fixed by updating either the Autoconf macros or the `configure.in' file for that package.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| webmaster donations bookstore | delorie software privacy |
| Copyright © 2003 by The Free Software Foundation | Updated Jun 2003 |