2004-05-03 11:59:46 +01:00
|
|
|
<?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;
|
|
|
|
]>
|
2004-01-27 22:29:49 +00:00
|
|
|
<sect1 id="ch-system-autoconf" xreflabel="Autoconf">
|
2004-05-03 11:59:46 +01:00
|
|
|
<title>Autoconf-&autoconf-version;</title>
|
|
|
|
<?dbhtml filename="autoconf.html"?>
|
|
|
|
|
|
|
|
<indexterm zone="ch-system-autoconf"><primary sortas="a-Autoconf">Autoconf</primary></indexterm>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2004-01-12 23:23:50 +00:00
|
|
|
<para>The Autoconf package contains programs for producing shell scripts that
|
|
|
|
can automatically configure source code.</para>
|
|
|
|
|
2004-05-03 11:59:46 +01:00
|
|
|
<screen>&buildtime; 0.5 SBU
|
|
|
|
&diskspace; 7.7 MB</screen>
|
|
|
|
|
|
|
|
<para>Autoconf installation depends on: Bash, Coreutils, Diffutils, Grep,
|
|
|
|
M4, Make, Perl, Sed.</para>
|
2001-07-17 19:51:18 +01:00
|
|
|
|
2003-11-01 22:31:50 +00:00
|
|
|
|
|
|
|
<sect2>
|
|
|
|
<title>Installation of Autoconf</title>
|
|
|
|
|
|
|
|
<para>Prepare Autoconf for compilation:</para>
|
|
|
|
|
|
|
|
<screen><userinput>./configure --prefix=/usr</userinput></screen>
|
|
|
|
|
|
|
|
<para>Compile the package:</para>
|
|
|
|
|
|
|
|
<screen><userinput>make</userinput></screen>
|
|
|
|
|
2004-05-03 11:59:46 +01:00
|
|
|
<para>To test the results, issue:
|
2004-02-09 22:44:26 +00:00
|
|
|
<userinput>make check</userinput>. This takes a long time, about 2 SBUs.</para>
|
2003-11-01 22:31:50 +00:00
|
|
|
|
2004-05-03 11:59:46 +01:00
|
|
|
<para>Install the package:</para>
|
2003-11-01 22:31:50 +00:00
|
|
|
|
|
|
|
<screen><userinput>make install</userinput></screen>
|
|
|
|
|
|
|
|
</sect2>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
2004-01-12 23:23:50 +00:00
|
|
|
|
2004-05-03 11:59:46 +01:00
|
|
|
<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>
|
2003-11-01 22:31:50 +00:00
|
|
|
|
2004-05-03 11:59:46 +01:00
|
|
|
<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>
|