AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update 'Working in a Chromium repo' documentation.

Browse Source 
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 <halcanary@google.com>
Commit-Queue: Hal Canary <halcanary@google.com>
This commit is contained in:
Bryce Thomas 2018-04-04 22:49:06 -07:00 committed by Skia Commit-Bot
parent c5f0427f14
commit 0aa81241e3
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
site/dev/chrome/repo.md
View File

@ -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;