News for hackers. Stuff that matters.
Re:Additional C/C++ Tooling by mden on Friday July 24, 2015 @08:56PM (#9946134)
Our team has had a decent compile time improvement by switching to ninja[1] from gmake.

[1] https://martine.github.io/ninja/manual.html

Re:Additional C/C++ Tooling by Joky on Friday July 24, 2015 @09:29PM (#9946208)
My experience has been very positive for incremental build (you have built once a large software and change one file and need to rebuild) but no difference on fresh build.
Re:Additional C/C++ Tooling by mahyarm on Friday July 24, 2015 @10:02PM (#9946261)
After a certain point, you can't get over compiler processing time.
Re:Additional C/C++ Tooling by mden on Friday July 24, 2015 @11:20PM (#9946416)
Ninja's magic happens before the compiler in deciding what needs to be compiled quicker than gmake.
Re:Additional C/C++ Tooling by mahyarm on Saturday July 25, 2015 @02:00PM (#9948385)
That's what I meant. If you have to rebuild everything, then ninja or gmake doesn't make anything faster, since it's the compiler's speed at that point.
Re:Additional C/C++ Tooling by Joky on Sunday July 26, 2015 @03:59PM (#9952029)
Well there is still the amount of parallelism that can be exposed. It just seems that CMake exposes it as well for make than for ninja I guess.
Re:Additional C/C++ Tooling by mden on Friday July 24, 2015 @11:19PM (#9946414)
Yup exactly what we use it for. Combined with Jenkins, makes it easy to make sure your master branch is in a good state.
Re:Additional C/C++ Tooling by dima55 on Friday July 24, 2015 @10:37PM (#9946330)
If you mean as a backend to CMake, then it's entirely the fault of CMake's braindead-ness
Re:Additional C/C++ Tooling by mden on Friday July 24, 2015 @11:22PM (#9946422)
Explain. You are saying CMake is bad with gmake but good with ninja?
Re:Additional C/C++ Tooling by vezzy-fnord on Friday July 24, 2015 @09:59PM (#9946254)
No build system thus far reaches the elegance of redo, though.