Re: [chromium-dev] webcore_bindings target builds slowly

2009-12-03 Thread Jens Alfke
I filed a bug on this, including a proposal for how to improve build  
times by breaking DerivedSourcesAllInOne into four pieces (with a  
workaround to keep it building all-in-one for configurations that  
require that.)

https://bugs.webkit.org/show_bug.cgi?id=32128

I'll do it, if people think it's a good idea...

—Jens

-- 
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev


Re: [chromium-dev] webcore_bindings target builds slowly

2009-12-01 Thread Lei Zhang
DerivedSourcesAllInOne.cpp is the biggest bottleneck on Linux too.
Even when running make with a high -j value, one would end up in the
situation where one core is pegged for more than a minutes while all
the others sit idle.

On Tue, Dec 1, 2009 at 10:57 AM, Lei Zhang  wrote:
> DerivedSourcesAllInOne.cpp is the biggest bottleneck on Linux too.
> Even when running make with a high -j value, one would end up in the
> situation where one core is pegged for more than a minutes while all
> the others sit idle.
>
> On Tue, Dec 1, 2009 at 9:32 AM, Jens Alfke  wrote:
>> On Mac* the WebCore Xcode project has a separate build target
>> "webcore_bindings" that contains DerivedSourcesAllInOne.cpp and a
>> handful of other files. This setup is really slowing down the build
>> process on my Mac Pro, because DerivedSourcesAllInOne takes much
>> longer to compile than any of the other sources in that target (since
>> it #includes about 100 .cpp files), so there's a long period where one
>> of the 8 cores is compiling that one file while the others are
>> twiddling their thumbs.
>>
>> (I notice this especially because I've been working on V8 bindings
>> stuff lately, so everything I touch tends to force that target to
>> rebuild.)
>>
>> This could be improved either by
>> a- merging this target in with the main WebCore target (didn't it use
>> to be that way?)
>> b- adding more files to this target to give the other cores something
>> to do
>> c- breaking up DerivedSourcesAllInOne into several pieces to compile
>> simultaneously
>>
>> Anyone have any thoughts about this? (Option c seems attractively easy
>> to do...)
>>
>> —Jens
>>
>> *maybe this applies to other platforms too, since the basic build
>> structure comes from the shared .gyp file?
>>
>> --
>> Chromium Developers mailing list: chromium-dev@googlegroups.com
>> View archives, change email options, or unsubscribe:
>>    http://groups.google.com/group/chromium-dev
>>
>

-- 
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev