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