Oh and a lot of warnings appeared recently. It is surprising how much warnings slow down the build, probably due to stdout serialization.
http://code.google.com/p/chromium/issues/detail?id=23039 M-A On Fri, Sep 25, 2009 at 9:18 AM, Marc-Antoine Ruel <[email protected]> wrote: > http://code.google.com/p/chromium/issues/detail?id=21266 > > This is a real problem, I just haven't looked into this one in > particular. Sometimes I just feel like renaming the dll... > > M-A > > On Thu, Sep 24, 2009 at 10:29 PM, Mohamed Mansour <[email protected]> wrote: >> Hey Ben, same here ... I see this additional message today (havn't seen it >> before) >> 59>LINK : C:\Sandbox\Code\Chrome\src\chrome\Debug\chrome.dll not found or >> not built by the last incremental link; performing full link >> >> Changing one file used to take me 5 minutes to build. But now it takes me >> ~10-15 minutes. >> -Mohamed >> >> >> On Thu, Sep 24, 2009 at 10:06 PM, Ben Goodger (Google) <[email protected]> >> wrote: >>> >>> I just ran a build here at home on my i7 workstation. It took 14 >>> minutes. This is the same system that would build in 7 minutes when I >>> set it up in May. >>> >>> What gives? We need to figure this out ASAP. >>> >>> -Ben >>> >>> >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
