| commit | f3726c61d205f7c5e96c201ad9d425ec811d35f3 | [log] [tgz] |
|---|---|---|
| author | Kevin Lubick <kjlubick@google.com> | Thu Nov 18 10:55:41 2021 -0500 |
| committer | Kevin Lubick <kjlubick@google.com> | Thu Nov 18 19:18:54 2021 +0000 |
| tree | ced565932b5de2f3ca26d90226325ecd76ac3642 | |
| parent | a5261995416e0af98403978ccdf18b910adf933b [diff] |
[infra] Use Bazel transitions to allow cc_binary to set their own flags This will hopefully let us pre-package certain binaries (e.g. DM, fuzz) with more sensible defaults and not make the developer type out all the settings. For CanvasKit, which specifies its own build flags, I think I'll need to make another transition setup, which would go in something like modules/canvaskit/ck_binary_with_flags.bzl or something. Some sausage-case-names were converted to snake_case_names as per go/build-style#target-naming The example this is based off is worth a look through before diving into this: https://github.com/bazelbuild/examples/tree/main/rules/starlark_configurations/cc_binary_selectable_copts Change-Id: Ia919d47f4d1aa25cf294af7918e36d38838c179e Bug: skia:12541 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/472688 Reviewed-by: Ben Wagner <bungeman@google.com> Reviewed-by: Leandro Lovisolo <lovisolo@google.com>