AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
1627c04d86
skia2/site/dev/chrome/repo.md
Hal Canary 30a6b81f4b Documentation: Consistancy 
* Don't rely on '#!', since it doesn't work for Windows cmd shell.
  * Consistantly use `tools/git-sync-deps` rather than `bin/sync`.
  * Always call `bin/gn` ranther than `gn` in case depot_tools is
    missing from the path.

NOTRY=true
Change-Id: I27909f2610d1bb3241874399d7d2f7286f99f43b
Reviewed-on: https://skia-review.googlesource.com/9640
Reviewed-by: Mike Klein <mtklein@chromium.org>
Commit-Queue: Mike Klein <mtklein@chromium.org>
2017-03-14 14:21:49 +00:00

716 B
Raw Blame History

Working in a Chromium repo

To work on Skia inside a Chromium checkout, run the following:

cd chromium/src/third_party/skia
python 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.