Add Waf build system as an alternative to autotools

[GoogleCodeExporter]

The autotools-base build systems generate lots of intermediate files, need an 
'autogen.sh' step before creating a distributable release, are slow, cryptic, 
and depend on the version of autotools installed on the build machine.

You end up inserting lots of awful stuff into the autoconf and automake sources 
to keep portability.

And I'm not talking about libtool hell.

For such a small project, it would be handy to have something more efficient, 
easier to maintain and extend, and that relies on as few external dependencies 
as possible.

Waf is designed that way, you only need python, that's all (and a C toolchain, 
obviously, because it is a C project). And since you include the waf script 
(i.e. the _whole_ build system) with the sources, you are certain everyone has 
the same version of the build system.

Here is a patch that adds the waf build system, a wscript (replaces ALL the 
configure and makefiles of the project in 31 lines) and updates README and NEWS 
accordingly.

Thanks for taking a few minutes to at least look at it before saying "It's not 
autotools, we don't want that", I'm sure you'll be convinced.

With kind regards,
Lionel

Original issue reported on code.google.com by lionel.orry@gmail.com on 24 Jun 2011 at 3:17

Attachments:

• opendpi_waf.diff