How will V8 bindings be handled - is it our intention that the burden of creating/maintaining V8 bindings will be shouldered by the WebKit community? Or is it expected that the Chromium port buildbot will just go red and chromium team members will step up to write bindings? Or perhaps the Chromium port will just use JS bindings (no V8)? The lack of WebKit trybots is a real obstacle to landing large patches/new files currently because I can't easily test the build-side changes on the GTK and Qt ports, and it sounds like that issue will be exacerbated for the Chromium port if we use the V8 bindings on the build bot.
-atw On Tue, Sep 8, 2009 at 2:19 PM, Yaar Schnitman <[email protected]> wrote: > Hi all, > > I'm working on the Webkit Chromium Port, an attempt at upstreaming a > chromium-specific build target into the webkit tree. This is a large project > that involves many steps (see: http://trac.webkit.org/wiki/Chromium). > I plan to do the following: > 1. Merge chromium's webkit/config.h.in into webkit's > WebKit/WebCore/config.h. These files have been forked in the past, and now > should be merged so they can be shared by both the chromium build and the > chromium port build processes. > > 2. Extract the ncpe, wtf and webcore targets out of chromium's > webkit/webkit.gyp and upstream them into gyp/gypi files that will be placed > in the webkit tree, so they can be shared by both chromium and the chromium > port. A side benefit will be that these configuration files will live closer > to the source files they control, which will allow easier code management > and enable atomic commits. > > 3. Create a new directory WebKit/WebKit/chromium, which will have the > chromium port's .gyp file and a DEPS file with minimal dependencies. A build > bot will use gclient to fetch the dependencies and then build the webkit > chromium port. > > Throughout this process, I plan to eliminate unnecessary dependencies, > contributing to the effort of making our builds faster. > > Suggestions, concerns and warnings will be appreciated. > > Yaar > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
