Next: Versioning Up: Setup
4.1 Initializing `configure'
Every `configure' script must call `AC_INIT' before doing anything
else. The only other required macro is `AC_OUTPUT' (Note: Output).
-- Macro: AC_INIT (PACKAGE, VERSION, [BUG-REPORT], [TARNAME])
Process any command-line arguments and perform various
initializations and verifications.
Set the name of the PACKAGE and its VERSION. These are typically
used in `--version' support, including that of `configure'. The
optional argument BUG-REPORT should be the email to which users
should send bug reports. The package TARNAME differs from
PACKAGE: the latter designates the full package name (e.g., `GNU
Autoconf'), while the former is meant for distribution tar ball
names (e.g., `autoconf'). It defaults to PACKAGE with `GNU '
stripped, lower-cased, and all characters other than alphanumerics
and underscores are changed to `-'.
It is preferable that the arguments of `AC_INIT' be static, i.e.,
there should not be any shell computation, but they can be
computed by M4.
The following M4 macros (e.g., `AC_PACKAGE_NAME'), output variables
(e.g., `PACKAGE_NAME'), and preprocessor symbols (e.g.,
`PACKAGE_NAME'), are defined by `AC_INIT':
Exactly `PACKAGE VERSION'.
If your `configure' script does its own option processing, it should
inspect `$@' or `$*' immediately after calling `AC_INIT', because other
Autoconf macros liberally use the `set' command to process strings, and
this has the side effect of updating `$@' and `$*'. However, we
suggest that you use standard macros like `AC_ARG_ENABLE' instead of
attempting to implement your own option processing. Note: Site
automatically generated by info2www