2003-01-16 22:33:06 +00:00
|
|
|
<sect2><title> </title><para> </para></sect2>
|
2002-06-04 12:30:14 +01:00
|
|
|
|
2003-01-16 22:33:06 +00:00
|
|
|
<sect2><title>Descriptions</title>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2003-08-31 11:50:05 +01:00
|
|
|
<para>(Last checked against version &autoconf-contversion;.)</para>
|
2003-01-16 22:33:06 +00:00
|
|
|
<sect3><title>Program file descriptions</title>
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect4><title>autoconf</title>
|
2002-05-23 18:00:34 +01:00
|
|
|
<para>autoconf is a tool for producing shell scripts that automatically
|
2001-01-24 00:31:17 +00:00
|
|
|
configure software source code packages to adapt to many kinds of
|
2002-09-28 22:08:29 +01:00
|
|
|
Unix-like systems. The configuration scripts produced by autoconf are
|
2002-05-23 18:00:34 +01:00
|
|
|
independent of autoconf when they are run, so their users do not need to
|
|
|
|
have autoconf.</para></sect4>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect4><title>autoheader</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The autoheader program can create a template file of C #define
|
2002-05-23 18:01:16 +01:00
|
|
|
statements for configure to use.</para></sect4>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-06-23 22:39:27 +01:00
|
|
|
<sect4><title>autom4te</title>
|
|
|
|
<para>autom4te runs GNU M4 on files.</para></sect4>
|
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect4><title>autoreconf</title>
|
2002-05-23 18:00:34 +01:00
|
|
|
<para>If there are a lot of autoconf-generated configure scripts, the
|
2002-09-28 22:08:29 +01:00
|
|
|
autoreconf program can save some work. It runs autoconf and
|
|
|
|
autoheader (where appropriate) repeatedly to remake the autoconf
|
2001-01-24 00:31:17 +00:00
|
|
|
configure scripts and configuration header templates in the directory
|
2002-02-06 23:15:46 +00:00
|
|
|
tree rooted at the current directory.</para></sect4>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect4><title>autoscan</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The autoscan program can help to create a configure.in file for
|
2002-09-28 22:08:29 +01:00
|
|
|
a software package. autoscan examines the source files in a directory
|
|
|
|
tree. If a directory is not specified on the command line, then the
|
|
|
|
current working directory is used. The source files are searched for
|
|
|
|
common portability problems and a configure.scan file is created to
|
|
|
|
serve as the preliminary configure.in for that package.</para></sect4>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect4><title>autoupdate</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The autoupdate program updates a configure.in file that calls
|
2002-05-23 18:00:34 +01:00
|
|
|
autoconf macros by their old names to use the current
|
2002-02-06 23:15:46 +00:00
|
|
|
macro names.</para></sect4>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
<sect4><title>ifnames</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>ifnames can help when writing a configure.in for a software
|
2001-01-24 00:31:17 +00:00
|
|
|
package. It prints the identifiers that the package already uses in C
|
|
|
|
preprocessor conditionals. If a package has already been set up to
|
2002-09-28 22:08:29 +01:00
|
|
|
have some portability, this program can help to determine what configure
|
|
|
|
needs to check. It may fill in some gaps in a configure.in file generated
|
|
|
|
by autoscan.</para></sect4>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
</sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2002-02-06 23:15:46 +00:00
|
|
|
</sect2>
|