From 978d0bffc413b67ead9db2d2816b916cf3d502ca Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Wed, 24 Sep 2003 22:29:16 +0000 Subject: Changing the style of the command descriptions in appendix A. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2879 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- appendixa/autoconf-desc.xml | 77 +++++++++++++++++++++------------------------ 1 file changed, 36 insertions(+), 41 deletions(-) (limited to 'appendixa/autoconf-desc.xml') diff --git a/appendixa/autoconf-desc.xml b/appendixa/autoconf-desc.xml index 8f6e08762..e529d5a77 100644 --- a/appendixa/autoconf-desc.xml +++ b/appendixa/autoconf-desc.xml @@ -3,49 +3,44 @@ Descriptions (Last checked against version &autoconf-contversion;.) + Program file descriptions -autoconf -autoconf is a tool for producing shell scripts that automatically -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 -have autoconf. - -autoheader -The autoheader program can create a template file of C #define -statements for configure to use. - -autom4te -autom4te runs GNU M4 on files. - -autoreconf -If there are a lot of autoconf-generated configure scripts, the -autoreconf program can save some work. It runs autoconf and -autoheader (where appropriate) repeatedly to remake the autoconf -configure scripts and configuration header templates in the directory -tree rooted at the current directory. - -autoscan -The autoscan program can help to create a configure.in file for -a software package. autoscan examines the source files in a directory -tree. If a directory is not specified on the command line, then the -current working directory is used. The source files are searched for -common portability problems and a configure.scan file is created to -serve as the preliminary configure.in for that package. - -autoupdate -The autoupdate program updates a configure.in file that calls -autoconf macros by their old names to use the current -macro names. - -ifnames -ifnames can help when writing a configure.in for a software -package. It prints the identifiers that the package already uses in C -preprocessor conditionals. If a package has already been set up to -have some portability, this program can help to determine what configure -needs to check. It may fill in some gaps in a configure.in file generated -by autoscan. + +autoconf is a tool for producing shell scripts +that automatically configure software source code packages to adapt to many +kinds of Unix-like systems. The configuration scripts it produces are +independent -- running them does not require the autoconf program. + +autoheader is a tool for creating template files +of C #define statements for configure to use. + +autom4te is a wrapper for the M4 macro +processor. + +autoreconf comes in handy when there are a lot +of autoconf-generated configure scripts around. The program runs autoconf and +autoheader repeatedly (where appropriate) to remake the autoconf configure +scripts and configuration header templates in a given directory tree. + +autoscan can help to create a +configure.in file for a software package. It examines +the source files in a directory tree, searching them for common portability +problems and creates a configure.scan file that serves as +as a preliminary configure.in for the package. + +autoupdate modifies a +configure.in file that still calls autoconf macros +by their old names to use the current macro names. + +ifnames can be helpful when writing a +configure.in for a software package. It prints the +identifiers that the package uses in C preprocessor conditionals. If a package +has already been set up to have some portability, this program can help to +determine what configure needs to check. It can fill +in some gaps in a configure.in file generated by +autoscan. + -- cgit v1.2.3-54-g00ecf