your comment backs up my point. all of these alternative build systems consistently re-solve
the exact same problems that autotools solved eons ago.
cmake *just* added support for cross-compiling (and it isnt even in any released version) ?
without even looking at anything else about cmake, that tells me the project is useless to me.
i'm not saying my needs are the same as everyone out there, just that you cant champion a
replacement for autotools if it isnt a replacement. i'm glad *you've* found it useful, but if
your target compiling audience is more than just you, then i feel sorry for those poor chaps
(where chaps != you).
the things i cite are just common examples ive come across quite frequently when dealing with
non-autotooled packages as a distribution maintainer (whether it be cmake or scons or hand
rolled or whatever). they certainly a complete list. i imagine there are numerous other
portability fixes autotools has which these "replacements" lack.
Posted Feb 7, 2008 23:22 UTC (Thu) by nix (subscriber, #2304)
[Link]
autoconf-generated configure scripts also support the godsends which are
site-config files. Nobody else seems to remember about that, which means
you need to wrap another build system around your build system just to get
your CFLAGS et al consistent.