|
UsingWebKitGit
Using WebKit from Git with Chrome
If you know how to use GitIf you git clone git.webkit.org into third_party/WebKit, you can use Git within your Chrome tree to work on WebKit. You just need to change one thing, described below: Setuphttp://trac.webkit.org/wiki/UsingGitWithWebKit describes git checkout steps for WebKit.
Updating
These commands only update the gclient branch of your git clone in third_party/WebKit. To ensure that your build is consistent between chromium and WebKit source and to ensure that you don't commit to the gclient branch, you can either update your current branch:
Sharing a top-level WebKit checkout in a Chromium checkoutGrab git-new-workdir at http://repo.or.cz/w/git.git/blob/HEAD:/contrib/workdir/git-new-workdir. cd path/to/chromium/src/third_party git-new-workdir path/to/WebKit/git/checkout WebKit The advantage of this is that you can avoid needing to maintain two separate WebKit checkouts. FAQQ. Why doesn't gclient sync work without any fiddling? A. Our DEPS specifies to only pull some subdirectories of third_party/WebKit. Git works with full trees, so we just pull the whole WebKit tree and tell gclient to leave the whole tree alone.http://code.google.com/p/chromium/wiki/UsingNewGit Q. How are branches the WebKit tree related to the Chromium build? A. The tools/sync-webkit-git.py script updates third_party/WebKit on the branch "gclient". Don't commit to the "gclient" branch, it might confuse the update script. The chromium make files build from what ever is on your filesystem, ie the build will reflect the current branch at build time. |
Are you planning to build your own layout out engine?