Sadly, mod_wombat is stalled because I cannot figure out autotools, nor can I find anyone who understands autotools. Apparently everything is built by copying the macros from something else and tweaking them.. and praying.
I am coming around to building it with SCons, or if Jan finishes it, his Lua based autotools replacement. I am pretty sure waiting for him to build it, them learning it, will be faster than making autotools do what I want (ie, work).
writebacks...
help from the blogosphere
Where's the code? Where's the problem statement? Be nice to us out here in the blogosphere and provide some links, so we can be nice to you :-)
There is always an automake user mailing list, if you are stuck ... otherwise, just asking on IRC of another related project that uses autotools is a good way to share experiences and get things done. What exactly are you trying to get done, anyway?
Indeed
Indeed, autotools is awful to use and maintain, except for packagers. I've always preferred scons or cmake. If you write your custom build based on scons, please don't forget to have DESTDIR support and don't hard-code paths such as "lib" (because it's lib64 on 64bit archs). Those are always painful for packagers.
I've given up on Make-based or Make-generator systems. SCons is pretty good but I've come around to start using Boost.Build @ http://boost.org/boost-build2/ (which is being reimplemented in Python). Its incredibly powerful but the docs are fairly formal and lacking in examples. I don't see a replacement that's coming close at this point in time so might be worth investing in unless you find SCons definitely does everything you want.
comment...