aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/dev/chrome/repo.md
diff options
context:
space:
mode:
authorGravatar hcm <hcm@google.com>2015-02-18 12:56:40 -0800
committerGravatar Commit bot <commit-bot@chromium.org>2015-02-18 12:56:40 -0800
commit193b1346552a49460488274cb91799c8b0c78181 (patch)
tree9dd4baad8a757681a121023075c253e36dc7de99 /site/dev/chrome/repo.md
parent606df7ad9835125639a1bfa5b9013d9b3b478c85 (diff)
managing chromes use section of docs
Diffstat (limited to 'site/dev/chrome/repo.md')
-rw-r--r--site/dev/chrome/repo.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/site/dev/chrome/repo.md b/site/dev/chrome/repo.md
new file mode 100644
index 0000000000..16cea6c8ab
--- /dev/null
+++ b/site/dev/chrome/repo.md
@@ -0,0 +1,19 @@
+How to manage a Skia repo inside a Chromium repo
+================================================
+
+To work on Skia inside a Chromium checkout, run the following:
+
+~~~~
+$ cd chromium/src/third_party/skia
+$ tools/git-sync-deps
+~~~~
+
+This command does a minimal "just sync the DEPS" emulation of gclient sync for
+Skia into chromium/src/third_party/skia/third_party. After that, make dm or
+./gyp_skia && ninja -C out/Debug dm in chromium/src/third_party/skia will get
+you rolling.
+
+We no longer recommend the .gclient file manipulation to have Chromium DEPS also
+sync Skia's DEPS. Most of those DEPS are for building and testing only;
+Chromium doesn't need any of them, and it can be confusing and problematic if
+they somehow get mixed into the Chromium build.