> Kind of reverse to the usual saying: all automake
> projects are unhappy - but they are unhappy in the same way, all
> CMake/scons/whatever projects [may] be happy (I'm not sure), but they are
> happy in their own way and demand induvidual approach.
Ok, I know I already replied to this, but I have to make one other comment here. automake projects are not all "unhappy in the same way." There are a lot of different ways of using autotools, and there is no standard.
For example, some projects use libtool. Other projects don't.
Some projects use autoconf, but not automake. The end result is that given a file name, I can't tell whether it's a generated file or an input file without digging around in the source tree and figuring out the overall structure.
Some projects have a shell file that you're expected to run before the build, to encapsulate the necessary autotools commands for that project. Other projects don't provide that.
Different versions of autotools behave differently-- sometimes something valid for one version is a syntax error for another.
In contrast, in CMake, there is one program-- CMake-- that you either have installed, or you don't. There is one way of doing things. That is real standardization.