Changeset 53ad30a for appendixa/autoconf-desc.xml
- Timestamp:
- 09/22/2001 04:09:47 PM (23 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, v3_1, v3_2, v3_3, 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:
- 6fb47f4
- Parents:
- eb33fb1
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
appendixa/autoconf-desc.xml
reb33fb1 r53ad30a 10 10 11 11 <sect3><title>autoconf</title> 12 13 12 <para>Autoconf is a tool for producing shell scripts that automatically 14 13 configure software source code packages to adapt to many kinds of 15 14 UNIX-like systems. The configuration scripts produced by Autoconf are 16 15 independent of Autoconf when they are run, so their users do not need to 17 have Autoconf.</para> 18 19 </sect3> 16 have Autoconf.</para></sect3> 20 17 21 18 <sect3><title>autoheader</title> 22 23 19 <para>The autoheader program can create a template file of C #define 24 statements for configure to use</para> 25 26 </sect3> 20 statements for configure to use</para></sect3> 27 21 28 22 <sect3><title>autoreconf</title> 29 30 23 <para>If there are a lot of Autoconf-generated configure scripts, the 31 24 autoreconf program can save some work. It runs autoconf (and 32 25 autoheader, where appropriate) repeatedly to remake the Autoconf 33 26 configure scripts and configuration header templates in the directory 34 tree rooted at the current directory.</para> 35 36 </sect3> 27 tree rooted at the current directory.</para></sect3> 37 28 38 29 <sect3><title>autoscan</title> 39 40 30 <para>The autoscan program can help to create a configure.in file for 41 31 a software package. autoscan examines source files in the directory … … 43 33 current directory if none is given. It searches the source files for 44 34 common portability problems and creates a file configure.scan which 45 is a preliminary configure.in for that package.</para> 46 47 </sect3> 35 is a preliminary configure.in for that package.</para></sect3> 48 36 49 37 <sect3><title>autoupdate</title> 50 51 38 <para>The autoupdate program updates a configure.in file that calls 52 Autoconf macros by their old names to use the current macro names.</para> 53 54 </sect3> 39 Autoconf macros by their old names to use the current 40 macro names.</para></sect3> 55 41 56 42 <sect3><title>ifnames</title> 57 58 43 <para>ifnames can help when writing a configure.in for a software 59 44 package. It prints the identifiers that the package already uses in C … … 61 46 have some portability, this program can help to figure out what its 62 47 configure needs to check for. It may help fill in some gaps in a 63 configure.in generated by autoscan.</para> 64 65 </sect3> 48 configure.in generated by autoscan.</para></sect3> 66 49 67 50 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.