One idea I've been thinking about is timing how long a clean build takes, and tracking that just as we do with other performance tests. The goal would be to notice when someone introduces an unnecessary dependency that slows the build. Obviously if it's needed, that's ok.
Chromium-XP does a full build each time, I wonder how easy it would be to plot its build times? On Thu, Feb 5, 2009 at 10:48 AM, Evan Martin <[email protected]> wrote: > I fear we have a have a couple long threads of headers that touch > everything. At one point we had something like: v8 bindings -> stats > table -> process_util -> process, which meant if you touched any of > our process-management code we'd rebuild all of WebKit's SVG bindings. > :~( > > For an especially painful build, try touching npapi.h. Apparently > most of our project depends on that file. > > On Thu, Feb 5, 2009 at 10:29 AM, John Abd-El-Malek <[email protected]> wrote: >> >> I've gone through the code and removed all such occurrences. This >> speeds up the build from 15 to 13 minutes (using /MP on quadcore with >> SSD). It also means that editing that file only rebuilds 36 files >> instead of 200. >> >> There shouldn't be any reason to include that file from a header. The >> reason this has happened is that people have ended up using structs >> that define the parameters of an IPC message with many parameters as >> member variables in classes. If this happens, then the struct should >> just be moved to its own file outside of render_messages.h. >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
