Changeset 2c094d6 for appendixa/autoconf-desc.xml
- Timestamp:
- 09/28/2002 09:08:29 PM (22 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, v4_0, v4_1, 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:
- 4d46e012
- Parents:
- f5cc1c17
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
appendixa/autoconf-desc.xml
rf5cc1c17 r2c094d6 12 12 <para>autoconf is a tool for producing shell scripts that automatically 13 13 configure software source code packages to adapt to many kinds of 14 Unix-like systems. 14 Unix-like systems. The configuration scripts produced by autoconf are 15 15 independent of autoconf when they are run, so their users do not need to 16 16 have autoconf.</para></sect4> … … 25 25 <sect4><title>autoreconf</title> 26 26 <para>If there are a lot of autoconf-generated configure scripts, the 27 autoreconf program can save some work. It runs autoconf (and28 autoheader ,where appropriate) repeatedly to remake the autoconf27 autoreconf program can save some work. It runs autoconf and 28 autoheader (where appropriate) repeatedly to remake the autoconf 29 29 configure scripts and configuration header templates in the directory 30 30 tree rooted at the current directory.</para></sect4> … … 32 32 <sect4><title>autoscan</title> 33 33 <para>The autoscan program can help to create a configure.in file for 34 a software package. autoscan examines source files in thedirectory35 tree rooted at a directory given as a command line argument, orthe36 current directory if none is given. It searches the source filesfor37 common portability problems and creates a file configure.scan which38 is apreliminary configure.in for that package.</para></sect4>34 a software package. autoscan examines the source files in a directory 35 tree. If a directory is not specified on the command line, then the 36 current working directory is used. The source files are searched for 37 common portability problems and a configure.scan file is created to 38 serve as the preliminary configure.in for that package.</para></sect4> 39 39 40 40 <sect4><title>autoupdate</title> … … 47 47 package. It prints the identifiers that the package already uses in C 48 48 preprocessor conditionals. If a package has already been set up to 49 have some portability, this program can help to figure out what its50 configure needs to check for. It may help fill in some gaps in a 51 configure.in generatedby autoscan.</para></sect4>49 have some portability, this program can help to determine what configure 50 needs to check. It may fill in some gaps in a configure.in file generated 51 by autoscan.</para></sect4> 52 52 53 53 </sect3>
Note:
See TracChangeset
for help on using the changeset viewer.