| 1 | <sect2><title> </title><para> </para></sect2>
|
|---|
| 2 |
|
|---|
| 3 | <sect2><title>Descriptions</title>
|
|---|
| 4 |
|
|---|
| 5 | <para>(Last checked against version &autoconf-contversion;.)</para>
|
|---|
| 6 |
|
|---|
| 7 | <sect3><title>Program file descriptions</title>
|
|---|
| 8 |
|
|---|
| 9 | <para><command>autoconf</command> is a tool for producing shell scripts
|
|---|
| 10 | that automatically configure software source code packages to adapt to many
|
|---|
| 11 | kinds of Unix-like systems. The configuration scripts it produces are
|
|---|
| 12 | independent -- running them does not require the autoconf program.</para>
|
|---|
| 13 |
|
|---|
| 14 | <para><command>autoheader</command> is a tool for creating template files
|
|---|
| 15 | of C #define statements for configure to use.</para>
|
|---|
| 16 |
|
|---|
| 17 | <para><command>autom4te</command> is a wrapper for the M4 macro
|
|---|
| 18 | processor.</para>
|
|---|
| 19 |
|
|---|
| 20 | <para><command>autoreconf</command> comes in handy when there are a lot
|
|---|
| 21 | of autoconf-generated configure scripts around. The program runs autoconf and
|
|---|
| 22 | autoheader repeatedly (where appropriate) to remake the autoconf configure
|
|---|
| 23 | scripts and configuration header templates in a given directory tree.</para>
|
|---|
| 24 |
|
|---|
| 25 | <para><command>autoscan</command> can help to create a
|
|---|
| 26 | <filename>configure.in</filename> file for a software package. It examines
|
|---|
| 27 | the source files in a directory tree, searching them for common portability
|
|---|
| 28 | problems and creates a <filename>configure.scan</filename> file that serves as
|
|---|
| 29 | as a preliminary <filename>configure.in</filename> for the package.</para>
|
|---|
| 30 |
|
|---|
| 31 | <para><command>autoupdate</command> modifies a
|
|---|
| 32 | <filename>configure.in</filename> file that still calls autoconf macros
|
|---|
| 33 | by their old names to use the current macro names.</para>
|
|---|
| 34 |
|
|---|
| 35 | <para><command>ifnames</command> can be helpful when writing a
|
|---|
| 36 | <filename>configure.in</filename> for a software package. It prints the
|
|---|
| 37 | identifiers that the package uses in C preprocessor conditionals. If a package
|
|---|
| 38 | has already been set up to have some portability, this program can help to
|
|---|
| 39 | determine what <userinput>configure</userinput> needs to check. It can fill
|
|---|
| 40 | in some gaps in a <filename>configure.in</filename> file generated by
|
|---|
| 41 | autoscan.</para>
|
|---|
| 42 |
|
|---|
| 43 | </sect3>
|
|---|
| 44 |
|
|---|
| 45 | </sect2>
|
|---|
| 46 |
|
|---|
