autoconf-desc.xml 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  1. <sect2><title>Contents of Autoconf</title>
  2. <para>Last checked against version &autoconf-contversion;.</para>
  3. <sect3><title>Program Files</title>
  4. <para>autoconf, autoheader, autom4te, autoreconf, autoscan, autoupdate and
  5. ifnames</para></sect3>
  6. <sect3><title>Descriptions</title>
  7. <sect4><title>autoconf</title>
  8. <para>autoconf is a tool for producing shell scripts that automatically
  9. configure software source code packages to adapt to many kinds of
  10. Unix-like systems. The configuration scripts produced by autoconf are
  11. independent of autoconf when they are run, so their users do not need to
  12. have autoconf.</para></sect4>
  13. <sect4><title>autoheader</title>
  14. <para>The autoheader program can create a template file of C #define
  15. statements for configure to use.</para></sect4>
  16. <sect4><title>autom4te</title>
  17. <para>autom4te runs GNU M4 on files.</para></sect4>
  18. <sect4><title>autoreconf</title>
  19. <para>If there are a lot of autoconf-generated configure scripts, the
  20. autoreconf program can save some work. It runs autoconf and
  21. autoheader (where appropriate) repeatedly to remake the autoconf
  22. configure scripts and configuration header templates in the directory
  23. tree rooted at the current directory.</para></sect4>
  24. <sect4><title>autoscan</title>
  25. <para>The autoscan program can help to create a configure.in file for
  26. a software package. autoscan examines the source files in a directory
  27. tree. If a directory is not specified on the command line, then the
  28. current working directory is used. The source files are searched for
  29. common portability problems and a configure.scan file is created to
  30. serve as the preliminary configure.in for that package.</para></sect4>
  31. <sect4><title>autoupdate</title>
  32. <para>The autoupdate program updates a configure.in file that calls
  33. autoconf macros by their old names to use the current
  34. macro names.</para></sect4>
  35. <sect4><title>ifnames</title>
  36. <para>ifnames can help when writing a configure.in for a software
  37. package. It prints the identifiers that the package already uses in C
  38. preprocessor conditionals. If a package has already been set up to
  39. have some portability, this program can help to determine what configure
  40. needs to check. It may fill in some gaps in a configure.in file generated
  41. by autoscan.</para></sect4>
  42. </sect3>
  43. </sect2>