| 1 | <sect2><title>Contents of Autoconf</title>
|
|---|
| 2 |
|
|---|
| 3 | <para>Last checked against version &autoconf-contversion;.</para>
|
|---|
| 4 |
|
|---|
| 5 | <sect3><title>Program Files</title>
|
|---|
| 6 | <para>autoconf, autoheader, autom4te, autoreconf, autoscan, autoupdate and
|
|---|
| 7 | ifnames</para></sect3>
|
|---|
| 8 |
|
|---|
| 9 | <sect3><title>Descriptions</title>
|
|---|
| 10 |
|
|---|
| 11 | <sect4><title>autoconf</title>
|
|---|
| 12 | <para>autoconf is a tool for producing shell scripts that automatically
|
|---|
| 13 | configure software source code packages to adapt to many kinds of
|
|---|
| 14 | Unix-like systems. The configuration scripts produced by autoconf are
|
|---|
| 15 | independent of autoconf when they are run, so their users do not need to
|
|---|
| 16 | have autoconf.</para></sect4>
|
|---|
| 17 |
|
|---|
| 18 | <sect4><title>autoheader</title>
|
|---|
| 19 | <para>The autoheader program can create a template file of C #define
|
|---|
| 20 | statements for configure to use.</para></sect4>
|
|---|
| 21 |
|
|---|
| 22 | <sect4><title>autom4te</title>
|
|---|
| 23 | <para>autom4te runs GNU M4 on files.</para></sect4>
|
|---|
| 24 |
|
|---|
| 25 | <sect4><title>autoreconf</title>
|
|---|
| 26 | <para>If there are a lot of autoconf-generated configure scripts, the
|
|---|
| 27 | autoreconf program can save some work. It runs autoconf and
|
|---|
| 28 | autoheader (where appropriate) repeatedly to remake the autoconf
|
|---|
| 29 | configure scripts and configuration header templates in the directory
|
|---|
| 30 | tree rooted at the current directory.</para></sect4>
|
|---|
| 31 |
|
|---|
| 32 | <sect4><title>autoscan</title>
|
|---|
| 33 | <para>The autoscan program can help to create a configure.in file for
|
|---|
| 34 | a software package. autoscan examines the source files in a directory
|
|---|
| 35 | tree. If a directory is not specified on the command line, then the
|
|---|
| 36 | current working directory is used. The source files are searched for
|
|---|
| 37 | common portability problems and a configure.scan file is created to
|
|---|
| 38 | serve as the preliminary configure.in for that package.</para></sect4>
|
|---|
| 39 |
|
|---|
| 40 | <sect4><title>autoupdate</title>
|
|---|
| 41 | <para>The autoupdate program updates a configure.in file that calls
|
|---|
| 42 | autoconf macros by their old names to use the current
|
|---|
| 43 | macro names.</para></sect4>
|
|---|
| 44 |
|
|---|
| 45 | <sect4><title>ifnames</title>
|
|---|
| 46 | <para>ifnames can help when writing a configure.in for a software
|
|---|
| 47 | package. It prints the identifiers that the package already uses in C
|
|---|
| 48 | preprocessor conditionals. If a package has already been set up to
|
|---|
| 49 | have some portability, this program can help to determine what configure
|
|---|
| 50 | needs to check. It may fill in some gaps in a configure.in file generated
|
|---|
| 51 | by autoscan.</para></sect4>
|
|---|
| 52 |
|
|---|
| 53 | </sect3>
|
|---|
| 54 |
|
|---|
| 55 | </sect2>
|
|---|
