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