On 5/25/13 12:45 PM, Mike Gilbert wrote:
> You may see small (~60 seconds) difference when compiling Chromium due
> to faster target dependency resolution.
You may also see faster builds in general because ninja is designed for
very high degree of parallelization as compared to make.
>> From a ma
On 5/25/13 9:17 PM, Tom Wijsman wrote:
On Sat, 25 May 2013 14:48:30 -0400
Mike Gilbert wrote:
For those unaware, dev-util/ninja is a make-replacement created by one
of the Chromium guys at Google. Its focus is on making incremental
builds of large software faster.
I've no idea how this would
On 05/25/2013 03:17 PM, Tom Wijsman wrote:
> From an user perspective I was wondering if ninja in the Portage tree
> makes use of this faster incremental builds feature. Should I expect
> faster builds when trying this out?
>
No, you will not see any significant speed increase because we always
s
On Sat, 25 May 2013 14:48:30 -0400
Mike Gilbert wrote:
> For those unaware, dev-util/ninja is a make-replacement created by one
> of the Chromium guys at Google. Its focus is on making incremental
> builds of large software faster.
I've no idea how this would work out, so I'm asking some questio
For those unaware, dev-util/ninja is a make-replacement created by one
of the Chromium guys at Google. Its focus is on making incremental
builds of large software faster.
In the latest chromium ebuild (chromium-29.0.1516.3), we are using ninja
instead of make. ninja auto-detects the number of jobs
