Ninja and KDevelop

[Andreas Pakulat]

Hi,

On Mon, Aug 20, 2012 at 12:31 AM, Aleix Pol <aleixpol at kde.org> wrote:
> On Sat, Aug 18, 2012 at 4:43 PM, Aleix Pol <aleixpol at kde.org> wrote:
>> I'm not in my system right now, I can try it later if you want. Or you
>> can just try it, it's easy to install (if you're in archlinux, yaourt
>> -S ninja-git). I think it's noticeably faster.
>>
> Ok, just tried it, I think there's quite a bit of a difference:

I tend to disagree, assuming this is a no-opt build which we hardly
ever encounter as developers, a difference of 5 vs. 2 seconds isn't
really that much. That being said, features such as

> Interesting things:
> - ninja takes care about the threading, so we can actually compile
> different jobs at the same time and not get the broken output.
> - ninja takes care about the process handling, so it will use as much
> parallel jobs as it thinks you need.

these two are for me a much more compelling reason to use ninja. So
far I didn't try it out since it did seem to be - at least in
combination with cmake - not quite mature enough for daily use.

Andreas