itchconfig Documentation
Basic Concepts


The use of itchconfig for a software package involves the following basic steps:

itchconfig tries to distinguish and separate the following items neatly:

In short: configure.base declares what shall be done, the resulting configure script determines how it is done.


When a package developer executes itchscan, this checks all files in the current directory and all sub-directories for the following:

From the results of these checks, itchscan generates the file configure.scan, which can be used as a starting point for a configure.base file. Please note that itchconfig can't yet process all commands which are generated by itchscan; so, before you put a command from configure.scan into configure.base, you should check (e.g. with the macro index) that the command has already been implemented.

When a package developer executes itchconfig, the following happens:

When a user executes configure, the following happens:

The file configure.base is some kind of central knowledge database for a software package. It contains information about all relevant specific needs and properties of the package - in a single place and encoded in m4 macro calls. (See the Macro Introduction.) itchconfig reads this database and creates a configure script file from it. itchconfig makes a special effort to minimize the size of that script, so that the overall package size isn't increased more than necessary and package users don't waste time when running the script. To achieve the design goals, the following ideas are realized:

This documentation file is part of version 0.0.4 of itchconfig, a configuration tool created by Arne Thomaßen. itchconfig is basically released under certain versions of the GNU General Public License and WITHOUT ANY WARRANTY. Copyright (C) 2002 Arne Thomaßen.