Now that we've got Hammer building the Windows version, and we've got a dependency DAG being enforced by checkdeps, is there anything holding us back from splitting up chrome.dll for Debug builds (or maybe some other build target initially)? It seems like the link time wins would be large, as would the instrumentation cycle for Purify.
The same goes for unit_tests, which has gotten larger than chrome.dll. (I know people feel we have too many separate unit tests already, but this should really be handled with smoketests.py anyway) Erik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
