diff options
author | Matthew Burgess <matthew@linuxfromscratch.org> | 2004-05-03 10:59:46 +0000 |
---|---|---|
committer | Matthew Burgess <matthew@linuxfromscratch.org> | 2004-05-03 10:59:46 +0000 |
commit | 673b0d84ba9591e07c0bdf0ee49d92eba10f502c (patch) | |
tree | 129e27a1450727b440da4378e0117a468eb9c25e /chapter06/autoconf.xml | |
parent | 287ea55da70ceb1f0990554b7db921d525fef816 (diff) |
* Merged newxml into HEAD
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3435 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/autoconf.xml')
-rw-r--r-- | chapter06/autoconf.xml | 82 |
1 files changed, 70 insertions, 12 deletions
diff --git a/chapter06/autoconf.xml b/chapter06/autoconf.xml index 7401d1ab3..07b6b5cbe 100644 --- a/chapter06/autoconf.xml +++ b/chapter06/autoconf.xml @@ -1,17 +1,24 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> <sect1 id="ch-system-autoconf" xreflabel="Autoconf"> -<title>Installing Autoconf-&autoconf-version;</title> -<?dbhtml filename="autoconf.html" dir="chapter06"?> +<title>Autoconf-&autoconf-version;</title> +<?dbhtml filename="autoconf.html"?> + +<indexterm zone="ch-system-autoconf"><primary sortas="a-Autoconf">Autoconf</primary></indexterm> <para>The Autoconf package contains programs for producing shell scripts that can automatically configure source code.</para> -<screen>&buildtime; &autoconf-time; -&diskspace; &autoconf-compsize;</screen> +<screen>&buildtime; 0.5 SBU +&diskspace; 7.7 MB</screen> + +<para>Autoconf installation depends on: Bash, Coreutils, Diffutils, Grep, +M4, Make, Perl, Sed.</para> -&aa-autoconf-down; -&aa-autoconf-dep; -<sect2><title> </title><para> </para></sect2> <sect2> <title>Installation of Autoconf</title> @@ -23,17 +30,68 @@ can automatically configure source code.</para> <screen><userinput>make</userinput></screen> -<para>To have the results tested, issue: +<para>To test the results, issue: <userinput>make check</userinput>. This takes a long time, about 2 SBUs.</para> -<para>And install the package:</para> +<para>Install the package:</para> <screen><userinput>make install</userinput></screen> </sect2> -&aa-autoconf-shortdesc; -&aa-autoconf-desc; -</sect1> +<sect2 id="contents-autoconf"><title>Contents of Autoconf</title> + +<para><emphasis>Installed programs</emphasis>: autoconf, autoheader, autom4te, +autoreconf, autoscan, autoupdate and ifnames</para> + +</sect2> + +<sect2><title>Short descriptions</title> + +<indexterm zone="ch-system-autoconf autoconf"><primary sortas="b-autoconf">autoconf</primary></indexterm> +<para id="autoconf"><command>autoconf</command> 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.</para> + +<indexterm zone="ch-system-autoconf autoheader"><primary sortas="b-autoheader">autoheader</primary></indexterm> +<para id="autoheader"><command>autoheader</command> is a tool for creating template files +of C #define statements for configure to use.</para> + +<indexterm zone="ch-system-autoconf autom4te"><primary sortas="b-autom4te">autom4te</primary></indexterm> +<para id="autom4te"><command>autom4te</command> is a wrapper for the M4 macro +processor.</para> +<indexterm zone="ch-system-autoconf autoreconf"><primary sortas="b-autoreconf">autoreconf</primary></indexterm> +<para id="autoreconf"><command>autoreconf</command> 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.</para> + +<indexterm zone="ch-system-autoconf autoscan"><primary sortas="b-autoscan">autoscan</primary></indexterm> +<para id="autoscan"><command>autoscan</command> can help to create a +<filename>configure.in</filename> file for a software package. It examines +the source files in a directory tree, searching them for common portability +problems and creates a <filename>configure.scan</filename> file that serves as +as a preliminary <filename>configure.in</filename> for the package.</para> + +<indexterm zone="ch-system-autoconf autoupdate"><primary sortas="b-autoupdate">autoupdate</primary></indexterm> +<para id="autoupdate"><command>autoupdate</command> modifies a +<filename>configure.in</filename> file that still calls autoconf macros +by their old names to use the current macro names.</para> + +<indexterm zone="ch-system-autoconf ifnames"><primary sortas="b-ifnames">ifnames</primary></indexterm> +<para id="ifnames"><command>ifnames</command> can be helpful when writing a +<filename>configure.in</filename> 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 <command>configure</command> needs to check. It can fill +in some gaps in a <filename>configure.in</filename> file generated by +autoscan.</para> + +</sect2> + + + +</sect1> |