Kevin Lubick f3726c61d2 [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>		2021-11-18 19:18:54 +00:00
..
common_config_settings	[canvaskit] Expand Bazel rules to include Canvas2D compat layer	2021-11-17 13:06:35 +00:00
BUILD.bazel	[infra] Add initial platforms and constraint values	2021-10-26 18:27:13 +00:00
cc_binary_with_flags.bzl	[infra] Use Bazel transitions to allow cc_binary to set their own flags	2021-11-18 19:18:54 +00:00
macros.bzl	[canvaskit] Add Freetype/Fonts to Bazel Build	2021-11-17 13:06:35 +00:00