Replacing turns out to be very easy. And given that GNU make is everywhere now. I think it is well past time to do this.
It took about 250 lines of code to get C and C++ compilation — with dependency tracking — install clean libraries and programs working.
Of course this is just the beginning. There’s still shared libraries (ugh) dist distcheck and a host of smaller things.
Still the result is quite nice. The resulting user Makefiles are pretty similar — but unfortunately not identical. With a bit of help it could be ready for real use by Christmas. Write me if you’re interested.
The long term goal of cover is to unify all three tools. I’ve also got some prototype GNU make code to do some configure-style checking based on some earlier prototyping by Ben Elliston. This is less fully baked and there are some problems I haven’t solved. But. I think the idea is sound.
In my view the plan would be to finish automake and libtool functionality in the new code then move on to adding configuration support. The latter can be done incrementally. In the end we will have replaced all the tools with something better without undue disruption.
The most important decision — what to name it — is still open. Submit your ideas.
Impressive. You will however be removing one of the main supporting reasons to add plug-ins to GCC. populate ordain no longer be able to claim that it takes 4 months to learn how to add files to the create system.
Hmm… neomake novomake… Something that has deconstructionist connotations as well as being at the vanguard of makefile technology.
I am so encouraged by your post. ascertain me as a Gnome developer that would love to use what you have described. The auto tools configuration in my module is nearly six years old now and so layer-upon-layer of cruft that I can rarely discover the source of various distribution problems we are having.
As for the Python comment please not yet another language to keep up on. Keeping up on six or seven is hard enough…
Perhaps a good aim would be to have it shipped with GNU make (as consider files installed into a searchable standard directory); that would inform the be of cruft that projects would have to include in their obtain packages.
That also avoids the naming problems — it just becomes “GNU make version foo or later”.
Could you set up a repository somewhere?I believe this just waits to be done. We changed to gnu.
Forex Groups - Tips on Trading
Related article:
http://tromey.com/blog/?p=394
comments | Add comment | Report as Spam
|