Jan,

> -----Original Message-----
> From: Jan Mikkelsen [mailto:janm@...]
> Sent: Thursday, 27 July 2000 10:23

> Unless someone has already done it, I'm going to throw away the current
> build system and create Makefiles for our in-house build system. Beyond
> that, I think there will be cruft removal and cleanup before any more
> functionality is added.

Are you familiar with GNU Autoconf? I'm not particularly except to note that
most good open source projects use it to manage the platform specific
configuration issues. (some examples; Samba, Perl).

It might be worth a look at before embarking on this project if you have the
time and energy :)

The following is from the GNU Autoconf home page
http://www.gnu.org/software/autoconf/autoconf.html
----------------------------------------------------
Introduction to Autoconf

Autoconf is an extensible package of m4 macros that produce shell scripts to
automatically configure software source code packages. These scripts can
adapt the packages to many kinds of UNIX-like systems without manual user
intervention. Autoconf creates a configuration script for a package from a
template file that lists the operating system features that the package can
use, in the form of m4 macro calls.

Producing configuration scripts using Autoconf requires GNU m4. You must
install GNU m4 (version 1.1 or later, preferably 1.3 or later for better
performance) before configuring Autoconf, so that Autoconf's configure
script can find it. The configuration scripts produced by Autoconf are
self-contained, so their users do not need to have Autoconf (or GNU m4).

Also, some optional utilities that come with Autoconf use Perl, TCL, and the
TCL packages Expect and DejaGNU. However, none of those are required in
order to use the main Autoconf program. If they are not present, the
affected Autoconf utilities will not be installed.
---------------------------------------------------

Cheers
Adam