| Joe Gregorio | 02f7202 | 2021-03-27 10:12:45 -0400 | [diff] [blame] | 1 | |
| 2 | --- |
| 3 | title: "Working in a Chromium repo" |
| 4 | linkTitle: "Working in a Chromium repo" |
| 5 | |
| 6 | --- |
| 7 | |
| 8 | |
| 9 | To work on Skia inside a Chromium checkout, run the following: |
| 10 | |
| 11 | cd chromium/src/third_party/skia |
| 12 | python2 tools/git-sync-deps |
| 13 | bin/gn gen out/Debug |
| 14 | |
| 15 | The second command does a minimal "just sync the DEPS" emulation of `gclient |
| 16 | sync` for Skia into chromium/src/third_party/skia/third_party. After that, |
| 17 | `ninja -C out/Debug dm` in chromium/src/third_party/skia will get you rolling. |
| 18 | |
| 19 | We no longer recommend the .gclient file manipulation to have Chromium DEPS also |
| 20 | sync Skia's DEPS. Most of those DEPS are for building and testing only; |
| 21 | Chromium doesn't need any of them, and it can be confusing and problematic if |
| 22 | they somehow get mixed into the Chromium build. |
| 23 | |