| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697 | <?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>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 thatcan automatically configure source code.</para><screen>&buildtime; 0.5 SBU&diskspace; 7.7 MB</screen><para>Autoconf installation depends on: Bash, Coreutils, Diffutils, Grep,M4, Make, Perl, Sed.</para><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><para>To test the results, issue:<userinput>make check</userinput>. This takes a long time, about 2 SBUs.</para><para>Install the package:</para><screen><userinput>make install</userinput></screen></sect2><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 scriptsthat automatically configure software source code packages to adapt to manykinds of Unix-like systems. The configuration scripts it produces areindependent -- 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 filesof 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 macroprocessor.</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 lotof autoconf-generated configure scripts around. The program runs autoconf andautoheader repeatedly (where appropriate) to remake the autoconf configurescripts 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 examinesthe source files in a directory tree, searching them for common portabilityproblems and creates a <filename>configure.scan</filename> file that serves asas 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 macrosby 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 theidentifiers that the package uses in C preprocessor conditionals. If a packagehas already been set up to have some portability, this program can help todetermine what <command>configure</command> needs to check. It can fillin some gaps in a <filename>configure.in</filename> file generated byautoscan.</para></sect2></sect1>
 |