autoconf-desc.xml 2.1 KB

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