autoconf-desc.xml 1.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. <sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
  2. <sect2><title>Short descriptions</title>
  3. <para><command>autoconf</command> is a tool for producing shell scripts
  4. that automatically configure software source code packages to adapt to many
  5. kinds of Unix-like systems. The configuration scripts it produces are
  6. independent -- running them does not require the autoconf program.</para>
  7. <para><command>autoheader</command> is a tool for creating template files
  8. of C #define statements for configure to use.</para>
  9. <para><command>autom4te</command> is a wrapper for the M4 macro
  10. processor.</para>
  11. <para><command>autoreconf</command> comes in handy when there are a lot
  12. of autoconf-generated configure scripts around. The program runs autoconf and
  13. autoheader repeatedly (where appropriate) to remake the autoconf configure
  14. scripts and configuration header templates in a given directory tree.</para>
  15. <para><command>autoscan</command> can help to create a
  16. <filename>configure.in</filename> file for a software package. It examines
  17. the source files in a directory tree, searching them for common portability
  18. problems and creates a <filename>configure.scan</filename> file that serves as
  19. as a preliminary <filename>configure.in</filename> for the package.</para>
  20. <para><command>autoupdate</command> modifies a
  21. <filename>configure.in</filename> file that still calls autoconf macros
  22. by their old names to use the current macro names.</para>
  23. <para><command>ifnames</command> can be helpful when writing a
  24. <filename>configure.in</filename> for a software package. It prints the
  25. identifiers that the package uses in C preprocessor conditionals. If a package
  26. has already been set up to have some portability, this program can help to
  27. determine what <userinput>configure</userinput> needs to check. It can fill
  28. in some gaps in a <filename>configure.in</filename> file generated by
  29. autoscan.</para>
  30. </sect2>