It would be great if kdevelop properly supported the ninja (http://martine.github.com/ninja) build tool. It seems like support shouldn't be hard, as ninja is mostly like make, except that: a. building subtargets must be done by giving the name of a subtarget rather than descending into a subdirectory. b. '-k' needs to be '-k <num>, where <num> is the number of errors to permit (INT_MAX is probably best until/unless modifying the GUI to allow a number to be specified). Right now I am using ninja by telling kdevelop that the 'make' binary is spelled 'ninja', which works well enough for top-level builds, but has no subtarget support.
since none of us developers use that yet, you should probably try to patch kdevelop yourself and send the patch to git.reviewboard.kde.org to get it in. otherwise you'll potentially have to wait quite a long time - just saying. cheers
https://projects.kde.org/projects/playground/devtools/plugins/kdev-ninja?jump=welcome I hope this helps.
Er... yes and no. When will this be either part of the official release or at least picked up and packaged by distributions? I'm not sure "...only if you build from source" qualifies as "fixed".
...and looking closer at that, it is impossible to package, as there are no release tarballs and kde.org does not (or not that I could figure out, anyway) provide git archive tarballs. Thus, it is not usable except by manually checking out the source code, which is not suitable for end users. Thus, not fixed.
KDevelop 4.5 contains a setting to use ninja build instead of make under "Configure KDevelop"->CMake, so I guess the plugin is no longer needed? Would be nice if the build system could be set for each project instead of being a global setting, because then you can gradually change to ninja without having to re-compile all projects at once. Also, exiv2 for example does not build with ninja on my system. The per-project build configuration also has no "Make" tab anymore when using ninja, and the "Make" tab was also used to set things like the number of threads.
That setting is only for newly generated build directories. When you decide to use ninja, but you have a make build directory configured, make is used. Also there's a ninja project configuration tab, but we don't support specifying the number of jobs in ninja, I considered it not very useful. In any case, this is a different thing than what the bug report so please open a new one if you think there are more things to discuss
I'm going to close this as ninja support is integrated now... If anyone objects, squawk and I can re-open it.