Re:Introduction to the Autotools (2012)
by highwind on Sunday January 31, 2016 @08:13AM
(#11006278)
Could you provide some examples of other choices that you speak of? Thank you.
[ Parent
| on HN ]
Re:Introduction to the Autotools (2012)
by rhodysurf on Sunday January 31, 2016 @09:36AM
(#11006498)
Cmake and Scons
Re:Introduction to the Autotools (2012)
by misframer on Sunday January 31, 2016 @09:37AM
(#11006502)
Perhaps CMake?
Re:Introduction to the Autotools (2012)
by antonyme on Wednesday February 03, 2016 @05:03AM
(#11025668)
CMake, Scons, Ninja, Gyp
There are many more, but these are more viable alternatives to auto tools.
https://en.wikipedia.org/wiki/List_of_build_automation_softw...
Premake (https://premake.github.io/)
waf (https://waf.io/)
Re:Introduction to the Autotools (2012)
by JoshTriplett on Sunday January 31, 2016 @04:10PM
(#11008083)
Please don't use waf. It does not provide a stable API from version to version, and encourages projects to embed a binary compiled version of waf. Unlike autotools, where you can ship configure.ac and Makefile.am and expect developers to run autoreconf after obtaining the project from version control, you can't easily do the same thing with waf due to the lack of versioning.
"Binary compiled"? Isn't waf a Python script?
Re:Introduction to the Autotools (2012)
by JoshTriplett on Sunday January 31, 2016 @10:45PM
(#11009611)
See the compiled version linked from the waf homepage, which projects using waf include in their source tree. That compiled version consists of a small Python stub followed by bz2-compressed data and a signature.