skia2/site/dev/chrome/repo.md
Mike Klein 2b8b06e793 rewrite docs to explicitly use python2
I don't particularly care about Python 2 vs 3,
and don't think we're likely to leave 2 soon.

Bug: skia:9079
Change-Id: Ia28c1312309d4d9218d05915dcd21a45fe6f3727
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/213506
Auto-Submit: Mike Klein <mtklein@google.com>
Reviewed-by: Heather Miller <hcm@google.com>
Commit-Queue: Mike Klein <mtklein@google.com>
2019-05-13 19:21:47 +00:00

18 lines
727 B
Markdown

Working in a Chromium repo
==========================
To work on Skia inside a Chromium checkout, run the following:
cd chromium/src/third_party/skia
python2 tools/git-sync-deps
bin/gn gen out/Debug
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;
Chromium doesn't need any of them, and it can be confusing and problematic if
they somehow get mixed into the Chromium build.