By last gyp Sverrir, do you mean the modules in chrome.sln switching over, or the ones in webkit?There was one generated set of targets in webkit.gyp, that we ended up adding a makefile emission option for. It was just too slow with rules (all the overhead of crossing over into cygwin per file). There are some rules in chrome.gyp that might have similar properties and would benefit from turning on the makefile option for those rules.
-BradN On Thu, Jun 11, 2009 at 7:40 AM, Sverrir Á. Berg <[email protected]>wrote: > Just wanted to echo Mohamed's findings. My build has been very slow the > past two weeks. I'm using VS2008 and I have not used /MP recently. I have > a top of the line machine (xw6600 Quad Core 8G mem, Intel SSD) and building > chrome.exe after a sync/clean takes approx 40 minutes. I think this > started approximately around the last gyp change... > > Sverrir > > > > On Thu, Jun 11, 2009 at 6:03 AM, nakro <[email protected]> wrote: > >> >> most of it will, but i never tried it >> >> however, i saw here in this forum ppl complaining that /MP on 2005 >> creates corrupted .PDB (the debug info) files >> so i don't know, but the incremental linking should work >> >> if you wish you can PM me and i will send you whatever you want >> (even the tool i wrote to make Cl.exe run in IDLE_PRIORITY_CLASS so i >> don't die while code compiles) >> >> but i just warn you that these things are not supported by chrome >> so do it at your own risk >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
