Submission + - Efficient Autotools Replacement?
eexaa writes: As you probably might have noticed, common ./configure script size grew to around half MB today, and even with simplest and smallest projects, running it can take around a minute on older/embedded system.
I was wondering that it would be nice to have a tool that can take input similar to autotools (list of targets to build and list of things to check for), can produce a configure script that isn't bloated (and doesn't explicitly check for all obsolete things that happened 20yrs ago), possibly lives without m4 (which is just plain ugly) and doesn't expect installation on user side (like SCons, CMake and other systems usually do). And yes, I believe that sacrificing some unneeded compatibility for efficiency would be fine today.
So — are any Slashdotters aware of some software or a set of mystic autotools tweaks that could help me solving this, or should I rather just sit down and code it?
I was wondering that it would be nice to have a tool that can take input similar to autotools (list of targets to build and list of things to check for), can produce a configure script that isn't bloated (and doesn't explicitly check for all obsolete things that happened 20yrs ago), possibly lives without m4 (which is just plain ugly) and doesn't expect installation on user side (like SCons, CMake and other systems usually do). And yes, I believe that sacrificing some unneeded compatibility for efficiency would be fine today.
So — are any Slashdotters aware of some software or a set of mystic autotools tweaks that could help me solving this, or should I rather just sit down and code it?
