Re:Scons - an autotools replacement and chrome's build tool
by dzorz on Thursday September 04, 2008 @01:40PM
(#294989)
Is there a recent comparison of cmake, scons and (boost) jam? I personally use cmake and it does its job well, but it has some flaws that aren't being fixed for some time...
[ Parent
| on HN ]
Re:Scons - an autotools replacement and chrome's build tool
by wheels on Thursday September 04, 2008 @02:21PM
(#295043)
The KDE project evaluated CMake and Scons (actually ported everything to Scons first), but ended up going for CMake. There's an article on it here:
http://lwn.net/Articles/188693/
I find QMake, even for projects that don't use Qt, really nice for projects that don't need to be packaged up or have complex dependancies. The format is trivial and it does well with generating makefiles, XCode projects or Visual Studio projects.
Re:Scons - an autotools replacement and chrome's build tool
by gcv on Thursday September 04, 2008 @03:35PM
(#295116)
I would also like to see an informed comparison. In addition to cmake, scons, qmake, and boost, there is also omake, which has an OCaml background but supports C, and waf, another Python build system. After skimming some documentation, I found it harder to compare autotools replacements than to compare various web frameworks. :)
Re:Scons - an autotools replacement and chrome's build tool
by s3graham on Friday September 05, 2008 @02:41AM
(#295631)
It depends a lot on your project. For large C++ projects, I've found scons and boost jam painfully slow for iterative builds. For smaller things they're possibly nice because they're expressive and pretty simple.
AFAIK, either make or vanilla jam is the fastest for C++, which is by far the most important thing to me, but that'll vary depending on your particular situation.
This is a bit old, but still accurate: http://www.gamesfromwithin.com/articles/0509/000100.html