1*c8dee2aaSAndroid Build Coastguard Worker 2*c8dee2aaSAndroid Build Coastguard Worker--- 3*c8dee2aaSAndroid Build Coastguard Workertitle: "Working in a Chromium repo" 4*c8dee2aaSAndroid Build Coastguard WorkerlinkTitle: "Working in a Chromium repo" 5*c8dee2aaSAndroid Build Coastguard Worker 6*c8dee2aaSAndroid Build Coastguard Worker--- 7*c8dee2aaSAndroid Build Coastguard Worker 8*c8dee2aaSAndroid Build Coastguard Worker 9*c8dee2aaSAndroid Build Coastguard WorkerTo work on Skia inside a Chromium checkout, run the following: 10*c8dee2aaSAndroid Build Coastguard Worker 11*c8dee2aaSAndroid Build Coastguard Worker cd chromium/src/third_party/skia 12*c8dee2aaSAndroid Build Coastguard Worker python3 tools/git-sync-deps 13*c8dee2aaSAndroid Build Coastguard Worker bin/gn gen out/Debug 14*c8dee2aaSAndroid Build Coastguard Worker 15*c8dee2aaSAndroid Build Coastguard WorkerThe second command does a minimal "just sync the DEPS" emulation of `gclient 16*c8dee2aaSAndroid Build Coastguard Workersync` for Skia into chromium/src/third_party/skia/third_party. After that, 17*c8dee2aaSAndroid Build Coastguard Worker`ninja -C out/Debug dm` in chromium/src/third_party/skia will get you rolling. 18*c8dee2aaSAndroid Build Coastguard Worker 19*c8dee2aaSAndroid Build Coastguard WorkerWe no longer recommend the .gclient file manipulation to have Chromium DEPS also 20*c8dee2aaSAndroid Build Coastguard Workersync Skia's DEPS. Most of those DEPS are for building and testing only; 21*c8dee2aaSAndroid Build Coastguard WorkerChromium doesn't need any of them, and it can be confusing and problematic if 22*c8dee2aaSAndroid Build Coastguard Workerthey somehow get mixed into the Chromium build. 23*c8dee2aaSAndroid Build Coastguard Worker 24