2022-05-04 15:53:40 +00:00
|
|
|
load("//bazel:macros.bzl", "cc_library", "exports_files_legacy", "select_multi")
|
[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
|
|
|
|
2022-04-14 18:01:45 +00:00
|
|
|
licenses(["notice"])
|
|
|
|
|
2022-05-04 15:53:40 +00:00
|
|
|
exports_files_legacy()
|
|
|
|
|
2022-03-08 20:27:12 +00:00
|
|
|
GENERAL_DEFINES = [
|
2022-05-03 14:11:06 +00:00
|
|
|
# The following comment is load-bearing. It will be replace via regex when we build for Google3
|
|
|
|
# Do not remove it or we won't be able to properly define SK_BUILD_FOR_GOOGLE3
|
|
|
|
# REPLACE_WHEN_BUILDING_IN_GOOGLE3
|
2022-03-08 20:27:12 +00:00
|
|
|
"SK_HAS_ANDROID_CODEC",
|
|
|
|
"SKIA_IMPLEMENTATION=1",
|
|
|
|
] + select({
|
[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
|
|
|
"//bazel/common_config_settings:debug_build": [
|
|
|
|
"SK_DEBUG",
|
|
|
|
],
|
|
|
|
"//bazel/common_config_settings:release_build": [
|
|
|
|
"SK_RELEASE",
|
|
|
|
],
|
|
|
|
"//conditions:default": [
|
|
|
|
"SK_RELEASE",
|
|
|
|
],
|
2022-02-04 20:04:15 +00:00
|
|
|
}) + select({
|
2022-04-11 19:22:51 +00:00
|
|
|
"//bazel/common_config_settings:enable_tracing_false": ["SK_DISABLE_TRACING"],
|
2022-02-04 20:04:15 +00:00
|
|
|
"//conditions:default": [],
|
|
|
|
}) + select({
|
2022-04-11 19:22:51 +00:00
|
|
|
"//bazel/common_config_settings:enable_effect_serialization_false": ["SK_DISABLE_EFFECT_DESERIALIZATION"],
|
2022-02-04 20:04:15 +00:00
|
|
|
"//conditions:default": [],
|
2022-02-09 18:14:25 +00:00
|
|
|
}) + select({
|
|
|
|
"//bazel/common_config_settings:is_skia_dev_build_true": [
|
|
|
|
"GR_TEST_UTILS=1",
|
|
|
|
"SK_ALLOW_STATIC_GLOBAL_INITIALIZERS=1",
|
|
|
|
],
|
|
|
|
"//conditions:default": [],
|
2022-04-08 15:29:33 +00:00
|
|
|
}) + select({
|
|
|
|
"//bazel/common_config_settings:enable_skslc_true": [
|
|
|
|
"SKSL_STANDALONE",
|
|
|
|
"SK_DISABLE_TRACING",
|
|
|
|
"SK_ENABLE_SPIRV_CROSS",
|
|
|
|
"SK_ENABLE_SPIRV_VALIDATION",
|
2022-05-05 23:35:55 +00:00
|
|
|
"SK_ENABLE_WGSL_VALIDATION",
|
2022-04-08 15:29:33 +00:00
|
|
|
],
|
|
|
|
"//conditions:default": [],
|
2022-04-12 12:23:07 +00:00
|
|
|
}) + select({
|
|
|
|
"//bazel/common_config_settings:enable_sksl_tracing_true": [
|
|
|
|
"SKSL_ENABLE_TRACING",
|
|
|
|
],
|
|
|
|
"//conditions:default": [],
|
[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
|
|
|
})
|
|
|
|
|
|
|
|
GPU_DEFINES = select({
|
|
|
|
"//bazel/common_config_settings:gl_backend": [
|
|
|
|
"SK_GL",
|
|
|
|
"SK_SUPPORT_GPU=1",
|
|
|
|
],
|
|
|
|
"//bazel/common_config_settings:vulkan_backend": [
|
|
|
|
"SK_VULKAN",
|
|
|
|
"SK_SUPPORT_GPU=1",
|
|
|
|
],
|
2022-03-21 17:06:32 +00:00
|
|
|
"//bazel/common_config_settings:dawn_backend": [
|
|
|
|
"SK_DAWN",
|
|
|
|
"SK_SUPPORT_GPU=1",
|
|
|
|
"VK_USE_PLATFORM_XCB_KHR", # TODO(kjlubick) support dawn's dawn_enable_vulkan etc
|
|
|
|
],
|
[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
|
|
|
"//conditions:default": [
|
|
|
|
"SK_SUPPORT_GPU=0",
|
|
|
|
],
|
|
|
|
}) + select({
|
|
|
|
"//bazel/common_config_settings:gl_standard": [
|
|
|
|
"SK_ASSUME_GL=1",
|
|
|
|
],
|
|
|
|
"//bazel/common_config_settings:gles_standard": [
|
|
|
|
"SK_ASSUME_GL_ES=1",
|
|
|
|
],
|
|
|
|
"//bazel/common_config_settings:webgl_standard": [
|
|
|
|
"SK_ASSUME_WEBGL=1",
|
|
|
|
"SK_USE_WEBGL",
|
|
|
|
],
|
|
|
|
"//conditions:default": [],
|
2022-04-05 18:21:56 +00:00
|
|
|
}) + select({
|
|
|
|
"//bazel/common_config_settings:vulkan_with_vma": [
|
|
|
|
"SK_USE_VMA",
|
|
|
|
],
|
|
|
|
"//conditions:default": [],
|
[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
|
|
|
})
|
|
|
|
|
|
|
|
CODEC_DEFINES = select_multi(
|
|
|
|
{
|
|
|
|
"//bazel/common_config_settings:gif_decode_codec": ["SK_HAS_WUFFS_LIBRARY"],
|
|
|
|
"//bazel/common_config_settings:jpeg_decode_codec": ["SK_CODEC_DECODES_JPEG"],
|
|
|
|
"//bazel/common_config_settings:jpeg_encode_codec": ["SK_ENCODE_JPEG"],
|
|
|
|
"//bazel/common_config_settings:png_decode_codec": ["SK_CODEC_DECODES_PNG"],
|
|
|
|
"//bazel/common_config_settings:png_encode_codec": ["SK_ENCODE_PNG"],
|
|
|
|
"//bazel/common_config_settings:raw_decode_codec": [
|
|
|
|
"SK_CODEC_DECODES_RAW",
|
|
|
|
"SK_CODEC_DECODES_JPEG",
|
|
|
|
],
|
|
|
|
"//bazel/common_config_settings:webp_decode_codec": ["SK_CODEC_DECODES_WEBP"],
|
2022-02-04 20:04:15 +00:00
|
|
|
"//bazel/common_config_settings:webp_encode_codec": ["SK_ENCODE_WEBP"],
|
[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
|
|
|
},
|
|
|
|
default = [],
|
|
|
|
)
|
|
|
|
|
|
|
|
PLATFORM_DEFINES = select({
|
|
|
|
"//bazel/common_config_settings:cpu_wasm": [
|
|
|
|
# working around https://github.com/emscripten-core/emscripten/issues/10072
|
|
|
|
"SK_FORCE_8_BYTE_ALIGNMENT",
|
|
|
|
"SK_DISABLE_LEGACY_SHADERCONTEXT",
|
2022-02-04 20:04:15 +00:00
|
|
|
"SK_DISABLE_AAA", # This saves about 57KB of code size, uncompressed
|
[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
|
|
|
],
|
|
|
|
"//conditions:default": [],
|
|
|
|
})
|
|
|
|
|
2021-11-30 20:59:32 +00:00
|
|
|
SHAPER_DEFINES = select_multi(
|
|
|
|
{
|
|
|
|
"//bazel/common_config_settings:coretext_shaper": ["SK_SHAPER_CORETEXT_AVAILABLE"],
|
|
|
|
"//bazel/common_config_settings:harfbuzz_shaper": ["SK_SHAPER_HARFBUZZ_AVAILABLE"],
|
|
|
|
},
|
|
|
|
default = [],
|
|
|
|
)
|
|
|
|
|
|
|
|
UNICODE_DEFINES = select({
|
|
|
|
"//bazel/common_config_settings:use_icu_true": ["SK_UNICODE_AVAILABLE"],
|
|
|
|
"//conditions:default": [],
|
|
|
|
})
|
|
|
|
|
[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
|
|
|
cc_library(
|
|
|
|
name = "defines_from_flags",
|
2021-11-30 20:59:32 +00:00
|
|
|
defines = GENERAL_DEFINES + GPU_DEFINES + CODEC_DEFINES + PLATFORM_DEFINES +
|
|
|
|
SHAPER_DEFINES + UNICODE_DEFINES,
|
[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
|
|
|
visibility = ["//:__subpackages__"],
|
|
|
|
)
|