Heads up: I'm gearing up to close the tree tonight for another attempt at
converting the webkit build to gyp, closure starting some time between 20:00
and 22:00 PDT. If this would be a serious imposition, let me know.
I'm still working on a few "last" issues. If I run into another serious
roadblock, there's a chance I'll wave off tonight. I'll send out another
announcement with final word on whether or not I'm going ahead, and at what
specific time, by COB today (~17:00 PDT).
In addition to fixing the layout test failures from last attempt, this
recent work has been trying to make sure all the dependency and source lists
(esp. including resources) are functionally equivalent, by isolating and
explaining any size discrepancies between VS-built and gyp-built .lib, .dll
and .exe files.
The most prominent change in the internal build architecture is that the V*
binding are longer built as as separate .lib (i.e., there's no separate
V8Bindings target), but are now part of webcore.lib.
I've been specifically verifying the following functionality:
- Debug builds from scratch
- Debug null rebuild (everything up to date)
- Release builds from scratch
- Release null rebuild (everything up to date)
- Tests that will be run by the buildbots all pass (or at least exhibit
the same failures as the vanilla VS build)
I specifically know that I haven't done anything to verify the following:
- Purify builds (erikkay, if there's something simple you or I can do to
sanity-check this ahead of time, let me know)
If you have some other piece of crucial functionality that really *must* be
verified as functioning correctly before we cut this over officially, please
let me know. We simply don't have a good central, list of every functional
piece that every script or other piece of infrastructure expects our build
to do (let alone what developer workflows expect...).
Barring some really disastrous problem, I'm planning to leave what we have
in place and recruit people to help hunt down and fix additional
discrepancies between the new and old builds (and will announce anything
known to be not working). The rate of change in the code base (especially
in the webkit.gyp and chrome.gyp files) means we simply have to get out of
trying to play a constant game of catch-up with this change.
Thanks,
--SK
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
