Algorithms for updating minimum spanning trees
After the shell code to recognize and respond to a system feature has been written, Autoconf allows it to be shared by many software packages that can use (or need) that feature.
If it later turns out that the shell code needs adjustment for some reason, it needs to be changed in only one place; all of the configuration scripts can be regenerated automatically to take advantage of the updated code.
The configuration scripts produced by Autoconf are independent of Autoconf when they are run, so their users do not need to have Autoconf.
The configuration scripts produced by Autoconf require no manual user intervention when run; they do not normally even need an argument specifying the system type.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover texts, and no Back-Cover Texts.
Autoconf requires GNU M4 version 1.4.6 or later in order to generate the scripts.Its components are typically shared at the source level, rather than being a library that gets built, installed, and linked against.The idea is to copy files from Gnulib into your own source tree.In this chapter, we introduce you to those tools, point you to sources of more information, and try to convince you to use the entire GNU build system for your software.means that a makefile is almost the only viable way to distribute automatic build rules for software, but one quickly runs into its numerous limitations.