2001-01-24 00:31:17 +00:00
|
|
|
<sect2>
|
|
|
|
<title>Contents</title>
|
|
|
|
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The Autoconf package contains the autoconf, autoheader, autoreconf,
|
|
|
|
autoscan, autoupdate and ifnames programs</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2><title>Description</title>
|
|
|
|
|
|
|
|
<sect3><title>autoconf</title>
|
2001-07-22 20:45:10 +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
|
|
|
|
UNIX-like systems. The configuration scripts produced by Autoconf are
|
|
|
|
independent of Autoconf when they are run, so their users do not need to
|
2001-09-22 17:09:47 +01:00
|
|
|
have Autoconf.</para></sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<sect3><title>autoheader</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The autoheader program can create a template file of C #define
|
2001-09-22 17:09:47 +01:00
|
|
|
statements for configure to use</para></sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<sect3><title>autoreconf</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>If there are a lot of Autoconf-generated configure scripts, the
|
2001-03-14 19:26:45 +00:00
|
|
|
autoreconf program can save some work. It runs autoconf (and
|
2001-01-24 00:31:17 +00:00
|
|
|
autoheader, where appropriate) repeatedly to remake the Autoconf
|
|
|
|
configure scripts and configuration header templates in the directory
|
2001-09-22 17:09:47 +01:00
|
|
|
tree rooted at the current directory.</para></sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<sect3><title>autoscan</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The autoscan program can help to create a configure.in file for
|
2001-01-24 00:31:17 +00:00
|
|
|
a software package. autoscan examines source files in the directory
|
|
|
|
tree rooted at a directory given as a command line argument, or the
|
|
|
|
current directory if none is given. It searches the source files for
|
|
|
|
common portability problems and creates a file configure.scan which
|
2001-09-22 17:09:47 +01:00
|
|
|
is a preliminary configure.in for that package.</para></sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<sect3><title>autoupdate</title>
|
2001-07-22 20:45:10 +01:00
|
|
|
<para>The autoupdate program updates a configure.in file that calls
|
2001-09-22 17:09:47 +01:00
|
|
|
Autoconf macros by their old names to use the current
|
|
|
|
macro names.</para></sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<sect3><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
|
2001-03-14 19:26:45 +00:00
|
|
|
have some portability, this program can help to figure out what its
|
2001-01-24 00:31:17 +00:00
|
|
|
configure needs to check for. It may help fill in some gaps in a
|
2001-09-22 17:09:47 +01:00
|
|
|
configure.in generated by autoscan.</para></sect3>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|