From 0aa81241e32d10d6d9b190b0d18645bd092e8bb6 Mon Sep 17 00:00:00 2001 From: Bryce Thomas Date: Wed, 4 Apr 2018 22:49:06 -0700 Subject: [PATCH] Update 'Working in a Chromium repo' documentation. No-Try: true Docs-Preview: https://skia.org/?cl=118521 Change-Id: Ibc639d10440ad449c875fe897af4f941fe4d4397 Reviewed-on: https://skia-review.googlesource.com/118521 Reviewed-by: Hal Canary Commit-Queue: Hal Canary --- site/dev/chrome/repo.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/site/dev/chrome/repo.md b/site/dev/chrome/repo.md index eaa658571a..e6418af1b5 100644 --- a/site/dev/chrome/repo.md +++ b/site/dev/chrome/repo.md @@ -5,11 +5,11 @@ To work on Skia inside a Chromium checkout, run the following: cd chromium/src/third_party/skia python tools/git-sync-deps + bin/gn gen out/Debug -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. +The second command does a minimal "just sync the DEPS" emulation of `gclient +sync` for Skia into chromium/src/third_party/skia/third_party. After that, +`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;