2021-11-16 19:09:44 +00:00
|
|
|
"""
|
|
|
|
This file contains general helper macros that make our BUILD.bazel files easier to read.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def select_multi(values_map, default, name = ""):
|
|
|
|
"""select() but allowing multiple matches of the keys.
|
|
|
|
|
|
|
|
select_multi works around a restriction in native select() that prevents multiple
|
|
|
|
keys from being matched unless one is a strict subset of another. For some features,
|
|
|
|
we allow multiple of that component to be active. For example, with codecs, we let
|
|
|
|
the clients mix and match anywhere from 0 built in codecs to all of them.
|
|
|
|
|
|
|
|
select_multi takes a given map and turns it into several distinct select statements
|
|
|
|
that have the effect of using any values associated with any active keys.
|
|
|
|
For example, if the following parameters are passed in:
|
|
|
|
values_map = {
|
|
|
|
":alpha": ["apple", "apricot"],
|
|
|
|
":beta": ["banana"],
|
|
|
|
":gamma": ["grapefruit"],
|
|
|
|
},
|
|
|
|
default = []
|
|
|
|
it will be unrolled into the following select statements
|
|
|
|
[] + select({
|
|
|
|
":apple": ["apple", "apricot"],
|
|
|
|
"//conditions:default": [],
|
|
|
|
}) + select({
|
|
|
|
":beta": ["banana"],
|
|
|
|
"//conditions:default": [],
|
|
|
|
}) + select({
|
|
|
|
":gamma": ["grapefruit"],
|
|
|
|
"//conditions:default": [],
|
|
|
|
})
|
|
|
|
|
|
|
|
Args:
|
|
|
|
values_map: dictionary of labels to a list of labels, just like select()
|
|
|
|
default: list of labels, the value that should be used if any of the options do not match.
|
|
|
|
This is typically an empty list
|
|
|
|
name: string unused, https://github.com/bazelbuild/buildtools/blob/master/WARNINGS.md#unnamed-macro
|
|
|
|
|
|
|
|
Returns:
|
|
|
|
A list of values that is filled in by the generated select statements.
|
|
|
|
"""
|
2021-11-11 17:50:02 +00:00
|
|
|
if len(values_map) == 0:
|
|
|
|
return default
|
|
|
|
rv = []
|
|
|
|
for key, value in values_map.items():
|
|
|
|
rv += select({
|
|
|
|
key: value,
|
|
|
|
"//conditions:default": default,
|
|
|
|
})
|
|
|
|
return rv
|
2021-11-23 14:01:28 +00:00
|
|
|
|
|
|
|
def generated_cc_atom(name, **kwargs):
|
|
|
|
"""A self-annotating label for a generated cc_library for exactly one file.
|
|
|
|
|
|
|
|
Args:
|
|
|
|
name: string, the name of the cc_library
|
|
|
|
**kwargs: All other arguments are passed verbatim to cc_library
|
|
|
|
"""
|
|
|
|
if len(kwargs.get("srcs", [])) > 1 or len(kwargs.get("hdrs", [])) > 1:
|
|
|
|
fail("Cannot have more than one src or hdr file in generated_cc_atom")
|
|
|
|
if len(kwargs.get("srcs", [])) > 0 and len(kwargs.get("hdrs", [])) > 0:
|
|
|
|
fail("Cannot set both srcs and hdrs in generated_cc_atom")
|
|
|
|
if len(kwargs.get("srcs", [])) == 0 and len(kwargs.get("hdrs", [])) == 0:
|
|
|
|
fail("Must set exactly one of srcs or hdrs in generated_cc_atom")
|
[bazel] Try adding cc_binary rules that use generated rules
To make the atomic rules a bit easier to work with, in many
of the folders, this adds in cc_library rules to group
together the sources from that folder (and subfolders
where prudent). We only needs sources because those atoms
should have their headers as deps.
One issue that was pointed out is that there is currently
no way to restrict the inclusion of certain packages,
a la, `gn check`. For example, there is no mechanism from
stopping a dev from adding
#include "modules/canvaskit/WasmCommon.h"
to something in //src/core (except circular dependencies).
We can probably address that using Bazel's visibility
rules as needed:
https://docs.bazel.build/versions/main/visibility.html
https://docs.bazel.build/versions/main/be/functions.html#package_group
It is recommended to look at this CL patchset by patchset.
PS1: Update gazelle command to generate rules in more folders.
PS2: A few changes to make generation work better.
PS3: The result of running make generate in //bazel
PS4: Adding the rules to build sksllex, the simplest binary I
could find in the Skia repo.
PS5: Adding the rules to build skdiff, a more complex binary.
I tried a few approaches, but ended up gravitating back
towards the layout where we have each folder/package
group up the sources. I imagine at some point, we'll have
skdiff depend on skia_core or something, which will
have things like //src/core, //src/codecs, //src/pathops
all bundled together.
PS7: Added in the groupings of sources, similar to what we had
earlier. I liked these for readability. These helped fix
up the //:skia_core build, and by extension, the CanvasKit
build.
Change-Id: I3faa7c4e821c876b243617aacf0246efa524cbde
Bug: skia:12541
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/476219
Reviewed-by: Ben Wagner <bungeman@google.com>
Reviewed-by: Leandro Lovisolo <lovisolo@google.com>
2021-11-30 13:15:24 +00:00
|
|
|
deps = kwargs.get("deps", [])
|
|
|
|
deps.append("//bazel:defines_from_flags")
|
|
|
|
kwargs["deps"] = deps
|
2021-11-23 14:01:28 +00:00
|
|
|
native.cc_library(
|
|
|
|
name = name,
|
|
|
|
**kwargs
|
|
|
|
)
|