Changeset 978d0bf for appendixa/autoconf-desc.xml
- Timestamp:
- 09/24/2003 10:29:16 PM (21 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 3a788f0c
- Parents:
- aa49729
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
appendixa/autoconf-desc.xml
raa49729 r978d0bf 4 4 5 5 <para>(Last checked against version &autoconf-contversion;.)</para> 6 6 7 <sect3><title>Program file descriptions</title> 7 <sect4><title>autoconf</title>8 <para>autoconf is a tool for producing shell scripts that automatically9 configure software source code packages to adapt to many kinds of10 Unix-like systems. The configuration scripts produced by autoconf are11 independent of autoconf when they are run, so their users do not need to12 have autoconf.</para></sect4>13 8 14 <sect4><title>autoheader</title> 15 <para>The autoheader program can create a template file of C #define 16 statements for configure to use.</para></sect4> 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> 17 13 18 < sect4><title>autom4te</title>19 <para>autom4te runs GNU M4 on files.</para></sect4>14 <para><command>autoheader</command> is a tool for creating template files 15 of C #define statements for configure to use.</para> 20 16 21 <sect4><title>autoreconf</title> 22 <para>If there are a lot of autoconf-generated configure scripts, the 23 autoreconf program can save some work. It runs autoconf and 24 autoheader (where appropriate) repeatedly to remake the autoconf 25 configure scripts and configuration header templates in the directory 26 tree rooted at the current directory.</para></sect4> 17 <para><command>autom4te</command> is a wrapper for the M4 macro 18 processor.</para> 27 19 28 <sect4><title>autoscan</title> 29 <para>The autoscan program can help to create a configure.in file for 30 a software package. autoscan examines the source files in a directory 31 tree. If a directory is not specified on the command line, then the 32 current working directory is used. The source files are searched for 33 common portability problems and a configure.scan file is created to 34 serve as the preliminary configure.in for that package.</para></sect4> 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> 35 24 36 <sect4><title>autoupdate</title> 37 <para>The autoupdate program updates a configure.in file that calls 38 autoconf macros by their old names to use the current 39 macro names.</para></sect4> 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> 40 30 41 <sect4><title>ifnames</title> 42 <para>ifnames can help when writing a configure.in for a software 43 package. It prints the identifiers that the package already uses in C 44 preprocessor conditionals. If a package has already been set up to 45 have some portability, this program can help to determine what configure 46 needs to check. It may fill in some gaps in a configure.in file generated 47 by autoscan.</para></sect4> 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> 48 42 49 43 </sect3> 50 44 51 45 </sect2> 46
Note:
See TracChangeset
for help on using the changeset viewer.