Algorithms for updating minimum spanning trees

Its lack of support for automatic dependency tracking, recursive builds in subdirectories, reliable timestamps (e.g., for network file systems), and so on, mean that developers must painfully (and often incorrectly) reinvent the wheel for each project.

There is no need to maintain files that list the features supported by each release of each variant of Posix.

For each software package that Autoconf is used with, it creates a configuration script from a template file that lists the system features that the package needs or can use.

Those who do not understand Autoconf are condemned to reinvent it, poorly.

The primary goal of Autoconf is making the package.

Instead, they individually test for the presence of each feature that the software package they are for might need.

(Before each check, they print a one-line message stating what they are checking for, so the user doesn't get too bored while waiting for the script to finish.) As a result, they deal well with systems that are hybrids or customized from the more common Posix variants.

It uses features that some versions of M4, including GNU M4 1.3, do not have.

Autoconf works better with GNU M4 version 1.4.14 or later, though this is not required.

The configuration scripts produced by Autoconf are independent of Autoconf when they are run, so their users do not need to have Autoconf.

Tags: , ,