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