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.
After a certain point, you can't get over compiler processing time.
Ninja's magic happens before the compiler in deciding what needs to be compiled quicker than gmake.
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.
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.
Yup exactly what we use it for. Combined with Jenkins, makes it easy to make sure your master branch is in a good state.
If you mean as a backend to CMake, then it's entirely the fault of CMake's braindead-ness
Explain. You are saying CMake is bad with gmake but good with ninja?
No build system thus far reaches the elegance of redo, though.