News for hackers. Stuff that matters.
Re:CopperSpice, a Modern C++ Fork of Qt by lmm on Tuesday June 09, 2015 @08:52AM (#9685570)
> Cross-platform portability obviously isn't their goal.

As someone who runs a couple of obscure platforms, I swear every time I have to use a non-Autotools project. Autotools may be slow and may check for seventeen different fortran compilers even if your project never uses fortran, but portability-wise it simply works.

Re:CopperSpice, a Modern C++ Fork of Qt by janoc on Tuesday June 09, 2015 @10:08AM (#9685972)
I suggest that everyone defending Autotools in this day and age actually reads one of these blogs (and check the date on them!):

http://freecode.com/articles/stop-the-autoconf-insanity-why-...

http://www.shlomifish.org/open-source/anti/autohell/

That should give you the idea why Autoconf/Automake setups are past their sell-by date. For more than a decade.

Re:CopperSpice, a Modern C++ Fork of Qt by lmm on Tuesday June 09, 2015 @10:42AM (#9686176)
I'm not unaware of those. Much of the first article's claims are simply false, and the second article's claims that CMake breaks less often than auto* are, uh, not borne out by my experience. (CMake is by no means the worst though; if you must use something non-autotools CMake is probably the best option). The facts simply don't match the rhetoric.
Re:CopperSpice, a Modern C++ Fork of Qt by amyjess on Tuesday June 09, 2015 @10:24AM (#9686065)
CMake is so wonderful. There's no reason to use it over autotools.