3 ms·
The comment "Put the blame where it belongs: Automake" below the original article sums it up pretty succinctly. Quoting: All the complaints in the article are
by nathell 13y ago
The comment "Put the blame where it belongs: Automake" below the original article sums it up pretty succinctly. Quoting:
All the complaints in the article are PRECISELY the kinds of complaints that autoconf programmers worked very hard to avoid. For example, it's IMPOSSIBLE to have version skew with autoconf because the configure script is completely pre-generated before being shipped. As far as the user is concerned it's a simple sh script.
ALL of these problems stem from the "automake" monstrosity that creates many more problems than it ever solved. Unfortunately people now tar autoconf with the same brush as automake and libtool whenever they run into problems with these. Sigh.
- sehugg 13y agoI'm seeing some projects shipping without configure which is annoying.
- MichaelMoser123 13y agoFor my projects I did a make system that uses gmake meta programming to easily define rules for most cases, here you have to includes a template make file that expands the target definitions into make rules. http://mosermichael.github.io/cstuff/all/projects/2011/06/17/make-system.html http://mosermichael.github.io/cstuff/all/projects/2011/06/17... The catch is of course most cases ; other stuff is still possible to do , but things become hacky. Another downside is cross compilation, my system does not do this effectively (though it works for Linux i686, x86_64 and Cygwin - many surprises between these setups !). Most build systems I know don't support cross compilation - except for automake, the terrible. If you do debian packages then you are strongly encouraged to use automake - because of cross compilation.