OLD | NEW |
1 How to manage a Skia repo inside a Chromium repo | 1 Working in a Chromium repo |
2 ================================================ | 2 ========================== |
3 | 3 |
4 To work on Skia inside a Chromium checkout, run the following: | 4 To work on Skia inside a Chromium checkout, run the following: |
5 | 5 |
6 ~~~~ | 6 ~~~~ |
7 $ cd chromium/src/third_party/skia | 7 $ cd chromium/src/third_party/skia |
8 $ tools/git-sync-deps | 8 $ tools/git-sync-deps |
9 ~~~~ | 9 ~~~~ |
10 | 10 |
11 This command does a minimal "just sync the DEPS" emulation of gclient sync for | 11 This command does a minimal "just sync the DEPS" emulation of gclient sync for |
12 Skia into chromium/src/third_party/skia/third_party. After that, make dm or | 12 Skia into chromium/src/third_party/skia/third_party. After that, make dm or |
13 ./gyp_skia && ninja -C out/Debug dm in chromium/src/third_party/skia will get | 13 ./gyp_skia && ninja -C out/Debug dm in chromium/src/third_party/skia will get |
14 you rolling. | 14 you rolling. |
15 | 15 |
16 We no longer recommend the .gclient file manipulation to have Chromium DEPS also | 16 We no longer recommend the .gclient file manipulation to have Chromium DEPS also |
17 sync Skia's DEPS. Most of those DEPS are for building and testing only; | 17 sync Skia's DEPS. Most of those DEPS are for building and testing only; |
18 Chromium doesn't need any of them, and it can be confusing and problematic if | 18 Chromium doesn't need any of them, and it can be confusing and problematic if |
19 they somehow get mixed into the Chromium build. | 19 they somehow get mixed into the Chromium build. |
OLD | NEW |