The easiest way to create a (mostly) complete configure.ac file is to run the
autoscan utility, which is part of the autoconf package. This utility examines the contents of a project directory and generates the basis for a configure.ac file (which
autoscan names configure.scan) using existing makefiles and source files.
Let's see how well
autoscan does on the Jupiter project. First, I'll clean up the droppings from my earlier experiments, and then run
autoscan in the jupiter directory. Note that I'm not deleting my original configure.ac file—I'll just let
autoscan tell me how to improve it. In less than a second, I have a few new files in the top-level directory:
rm -rf autom4te.cache build$
rm configure config.* ...