commit | fb74c17f6c344fd7b4f2cf0ecba5b69c550b698c | [log] [tgz] |
---|---|---|
author | Sunny Sachanandani <sunnyps@chromium.org> | Mon Apr 10 21:29:17 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 10 21:29:17 2023 |
tree | 465223ebb2a4188e9bf9ee74d5169c4ed740961c | |
parent | 4a3a79fe38a84fcee7c7fe3c1c7824b29c62e8ec [diff] |
gpu: Skia Graphite build and feature flags 1. Add build and feature flags for Graphite, both disabled by default. 2. Add skia_use_metal buildflag for guarding metal code. This flag is only enabled with Graphite on developer builds. 3. Add SkiaGraphiteBackend to GpuPreferences, and parse its value from feature and command line flags. Also add a kNone option for Ganesh GrContextType for when Graphite is enabled. 4. Cleanup Chromium Skia BUILD.gn - more consistency between the config and sources in how we use conditionals. Ensure dawn and metal code is only built when Graphite is used, and other miscellaneous cleanup. 5. Remove Ganesh Dawn from Chromium including in blink over WebGPU command buffer, so both Dawn and Metal are only used with Graphite. This doesn't yet rename the cc/viz pixel test enums - that will be a separate followup change since it would otherwise add a dozen or two more changed files to this CL. Bug: 1429361 Change-Id: Ibf129727e03c303bfac85b98c111b08d880f408f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4404275 Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Reviewed-by: Kevin Lubick <kjlubick@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Cr-Commit-Position: refs/heads/main@{#1128336}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.