2015-02-25 19:49:15 +00:00
|
|
|
Working in a Chromium repo
|
|
|
|
|
==========================
|
2015-02-18 20:56:40 +00:00
|
|
|
|
|
|
|
|
To work on Skia inside a Chromium checkout, run the following:
|
|
|
|
|
|
2017-03-14 14:03:51 +00:00
|
|
|
cd chromium/src/third_party/skia
|
2019-05-13 18:51:45 +00:00
|
|
|
python2 tools/git-sync-deps
|
2018-04-05 05:49:06 +00:00
|
|
|
bin/gn gen out/Debug
|
2015-02-18 20:56:40 +00:00
|
|
|
|
2018-04-05 05:49:06 +00:00
|
|
|
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.
|
2015-02-18 20:56:40 +00:00
|
|
|
|
|
|
|
|
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.
|
