| 1 | <sect2>
|
|---|
| 2 | <title>Contents</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>The Autoconf package contains the autoconf, autoheader, autoreconf,
|
|---|
| 5 | autoscan, autoupdate and ifnames programs</para>
|
|---|
| 6 |
|
|---|
| 7 | </sect2>
|
|---|
| 8 |
|
|---|
| 9 | <sect2><title>Description</title>
|
|---|
| 10 |
|
|---|
| 11 | <sect3><title>autoconf</title>
|
|---|
| 12 |
|
|---|
| 13 | <para>Autoconf is a tool for producing shell scripts that automatically
|
|---|
| 14 | configure software source code packages to adapt to many kinds of
|
|---|
| 15 | UNIX-like systems. The configuration scripts produced by Autoconf are
|
|---|
| 16 | independent of Autoconf when they are run, so their users do not need to
|
|---|
| 17 | have Autoconf.</para>
|
|---|
| 18 |
|
|---|
| 19 | </sect3>
|
|---|
| 20 |
|
|---|
| 21 | <sect3><title>autoheader</title>
|
|---|
| 22 |
|
|---|
| 23 | <para>The autoheader program can create a template file of C #define
|
|---|
| 24 | statements for configure to use</para>
|
|---|
| 25 |
|
|---|
| 26 | </sect3>
|
|---|
| 27 |
|
|---|
| 28 | <sect3><title>autoreconf</title>
|
|---|
| 29 |
|
|---|
| 30 | <para>If there are a lot of Autoconf-generated configure scripts, the
|
|---|
| 31 | autoreconf program can save some work. It runs autoconf (and
|
|---|
| 32 | autoheader, where appropriate) repeatedly to remake the Autoconf
|
|---|
| 33 | configure scripts and configuration header templates in the directory
|
|---|
| 34 | tree rooted at the current directory.</para>
|
|---|
| 35 |
|
|---|
| 36 | </sect3>
|
|---|
| 37 |
|
|---|
| 38 | <sect3><title>autoscan</title>
|
|---|
| 39 |
|
|---|
| 40 | <para>The autoscan program can help to create a configure.in file for
|
|---|
| 41 | a software package. autoscan examines source files in the directory
|
|---|
| 42 | tree rooted at a directory given as a command line argument, or the
|
|---|
| 43 | current directory if none is given. It searches the source files for
|
|---|
| 44 | common portability problems and creates a file configure.scan which
|
|---|
| 45 | is a preliminary configure.in for that package.</para>
|
|---|
| 46 |
|
|---|
| 47 | </sect3>
|
|---|
| 48 |
|
|---|
| 49 | <sect3><title>autoupdate</title>
|
|---|
| 50 |
|
|---|
| 51 | <para>The autoupdate program updates a configure.in file that calls
|
|---|
| 52 | Autoconf macros by their old names to use the current macro names.</para>
|
|---|
| 53 |
|
|---|
| 54 | </sect3>
|
|---|
| 55 |
|
|---|
| 56 | <sect3><title>ifnames</title>
|
|---|
| 57 |
|
|---|
| 58 | <para>ifnames can help when writing a configure.in for a software
|
|---|
| 59 | package. It prints the identifiers that the package already uses in C
|
|---|
| 60 | preprocessor conditionals. If a package has already been set up to
|
|---|
| 61 | have some portability, this program can help to figure out what its
|
|---|
| 62 | configure needs to check for. It may help fill in some gaps in a
|
|---|
| 63 | configure.in generated by autoscan.</para>
|
|---|
| 64 |
|
|---|
| 65 | </sect3>
|
|---|
| 66 |
|
|---|
| 67 | </sect2>
|
|---|
| 68 |
|
|---|
