diff options
| author | Mark Hymers <markh@linuxfromscratch.org> | 2001-09-22 16:09:47 +0000 |
|---|---|---|
| committer | Mark Hymers <markh@linuxfromscratch.org> | 2001-09-22 16:09:47 +0000 |
| commit | 53ad30a63b4d5f80f713963835dee995f9546071 (patch) | |
| tree | f304bfa899e693aa1f7de368f8e49ffe46477334 /appendixa/autoconf-desc.xml | |
| parent | eb33fb1cad428658dafc39e87d0c57ae479def5f (diff) | |
[Bug 190] Put descs in alphabetical order
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1249 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'appendixa/autoconf-desc.xml')
| -rw-r--r-- | appendixa/autoconf-desc.xml | 31 |
1 files changed, 7 insertions, 24 deletions
diff --git a/appendixa/autoconf-desc.xml b/appendixa/autoconf-desc.xml index b2df66adb..5fa4e6e0b 100644 --- a/appendixa/autoconf-desc.xml +++ b/appendixa/autoconf-desc.xml @@ -9,60 +9,43 @@ autoscan, autoupdate and ifnames programs</para> <sect2><title>Description</title> <sect3><title>autoconf</title> - <para>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.</para> - -</sect3> +have Autoconf.</para></sect3> <sect3><title>autoheader</title> - <para>The autoheader program can create a template file of C #define -statements for configure to use</para> - -</sect3> +statements for configure to use</para></sect3> <sect3><title>autoreconf</title> - <para>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.</para> - -</sect3> +tree rooted at the current directory.</para></sect3> <sect3><title>autoscan</title> - <para>The autoscan program can help to create a configure.in file for a software package. autoscan examines source files in the directory tree rooted at a directory given as a command line argument, or the current directory if none is given. It searches the source files for common portability problems and creates a file configure.scan which -is a preliminary configure.in for that package.</para> - -</sect3> +is a preliminary configure.in for that package.</para></sect3> <sect3><title>autoupdate</title> - <para>The autoupdate program updates a configure.in file that calls -Autoconf macros by their old names to use the current macro names.</para> - -</sect3> +Autoconf macros by their old names to use the current +macro names.</para></sect3> <sect3><title>ifnames</title> - <para>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 figure out what its configure needs to check for. It may help fill in some gaps in a -configure.in generated by autoscan.</para> - -</sect3> +configure.in generated by autoscan.</para></sect3> </sect2> |