autoconf: config.status Invocation
1
1 17 config.status Invocation
1 ***************************
1
1 The `configure' script creates a file named `config.status', which
1 actually configures, "instantiates", the template files. It also
1 records the configuration options that were specified when the package
1 was last configured in case reconfiguring is needed.
1
1 Synopsis:
1 ./config.status [OPTION]... [TAG]...
1
1 It configures each TAG; if none are specified, all the templates are
1 instantiated. A TAG refers to a file or other tag associated with a
11 configuration action, as specified by an `AC_CONFIG_ITEMS' macro (⇒
Configuration Actions). The files must be specified without their
1 dependencies, as in
1
1 ./config.status foobar
1
1 not
1
1 ./config.status foobar:foo.in:bar.in
1
1 The supported options are:
1
1 `--help'
1 `-h'
1 Print a summary of the command line options, the list of the
1 template files, and exit.
1
1 `--version'
1 `-V'
1 Print the version number of Autoconf and the configuration
1 settings, and exit.
1
1 `--config'
1 Print the configuration settings in reusable way, quoted for the
1 shell, and exit. For example, for a debugging build that
1 otherwise reuses the configuration from a different build
1 directory BUILD-DIR of a package in SRC-DIR, you could use the
1 following:
1
1 args=`BUILD-DIR/config.status --config`
1 eval SRC-DIR/configure "$args" CFLAGS=-g --srcdir=SRC-DIR
1
1 Note that it may be necessary to override a `--srcdir' setting
1 that was saved in the configuration, if the arguments are used in a
1 different build directory.
1
1 `--silent'
1 `--quiet'
1 `-q'
1 Do not print progress messages.
1
1 `--debug'
1 `-d'
1 Don't remove the temporary files.
1
1 `--file=FILE[:TEMPLATE]'
1 Require that FILE be instantiated as if
1 `AC_CONFIG_FILES(FILE:TEMPLATE)' was used. Both FILE and TEMPLATE
1 may be `-' in which case the standard output and/or standard
1 input, respectively, is used. If a TEMPLATE file name is
1 relative, it is first looked for in the build tree, and then in
1 the source tree. ⇒Configuration Actions, for more details.
1
1 This option and the following ones provide one way for separately
1 distributed packages to share the values computed by `configure'.
1 Doing so can be useful if some of the packages need a superset of
1 the features that one of them, perhaps a common library, does.
1 These options allow a `config.status' file to create files other
1 than the ones that its `configure.ac' specifies, so it can be used
1 for a different package, or for extracting a subset of values.
1 For example,
1
1 echo '@CC@' | ./config.status --file=-
1
1 provides the value of `@CC@' on standard output.
1
1 `--header=FILE[:TEMPLATE]'
1 Same as `--file' above, but with `AC_CONFIG_HEADERS'.
1
1 `--recheck'
1 Ask `config.status' to update itself and exit (no instantiation).
1 This option is useful if you change `configure', so that the
1 results of some tests might be different from the previous run.
1 The `--recheck' option reruns `configure' with the same arguments
1 you used before, plus the `--no-create' option, which prevents
1 `configure' from running `config.status' and creating `Makefile'
1 and other files, and the `--no-recursion' option, which prevents
1 `configure' from running other `configure' scripts in
1 subdirectories. (This is so other Make rules can run
1 `config.status' when it changes; ⇒Automatic Remaking, for
1 an example).
1
1 `config.status' checks several optional environment variables that
1 can alter its behavior:
1
1 -- Variable: CONFIG_SHELL
1 The shell with which to run `configure'. It must be
1 Bourne-compatible, and the absolute name of the shell should be
1 passed. The default is a shell that supports `LINENO' if
1 available, and `/bin/sh' otherwise.
1
1 -- Variable: CONFIG_STATUS
1 The file name to use for the shell script that records the
1 configuration. The default is `./config.status'. This variable is
1 useful when one package uses parts of another and the `configure'
1 scripts shouldn't be merged because they are maintained separately.
1
1 You can use `./config.status' in your makefiles. For example, in
1 the dependencies given above (⇒Automatic Remaking),
1 `config.status' is run twice when `configure.ac' has changed. If that
1 bothers you, you can make each run only regenerate the files for that
1 rule:
1 config.h: stamp-h
1 stamp-h: config.h.in config.status
1 ./config.status config.h
1 echo > stamp-h
1
1 Makefile: Makefile.in config.status
1 ./config.status Makefile
1
11 The calling convention of `config.status' has changed; see ⇒
Obsolete config.status Use, for details.
1