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