mirror of
https://github.com/bazelbuild/rules_cc
synced 2024-11-27 20:43:26 +00:00
48881f1f45
This is particularly relevant for Bzlmod, which currently uses the toolchains defined in rules_cc. As a result, Bazel C++ builds will use subtly different toolchains depending on whether --enable_bzlmod is used or not. This is fixed by loading toolchain detection logic from @bazel_tools in the module extension. Closes #163 PiperOrigin-RevId: 501199523 Change-Id: I01f263d37495d0c5dd070c8a32945898d1d639c5
43 lines
1.1 KiB
YAML
43 lines
1.1 KiB
YAML
---
|
|
x_defaults:
|
|
# YAML has a feature for "repeated nodes", BazelCI is fine with extra nodes
|
|
# it doesn't know about; so that is used to avoid repeating common subparts.
|
|
common: &common
|
|
# We have to list every package because even with exclusion notation -//foo
|
|
# Bazel will load the excluded package and it will be an error because at
|
|
# release Bazel the cc_libraries do not have all the attributes.
|
|
build_targets:
|
|
- "//:all"
|
|
- "//cc:all"
|
|
- "//cc/private/rules_impl:all"
|
|
- "//examples:all"
|
|
- "//examples/my_c_archive:all"
|
|
- "//examples/my_c_compile:all"
|
|
- "//examples/write_cc_toolchain_cpu:all"
|
|
- "//tools/migration:all"
|
|
test_flags:
|
|
- "--test_timeout=120"
|
|
test_targets:
|
|
- "//:all"
|
|
- "//cc:all"
|
|
- "//cc/private/rules_impl:all"
|
|
- "//examples:all"
|
|
- "//examples/my_c_archive:all"
|
|
- "//examples/my_c_compile:all"
|
|
- "//examples/write_cc_toolchain_cpu:all"
|
|
- "//tools/migration:all"
|
|
|
|
buildifier:
|
|
version: latest
|
|
warnings: "all"
|
|
|
|
tasks:
|
|
ubuntu1604:
|
|
<<: *common
|
|
ubuntu1804:
|
|
<<: *common
|
|
macos:
|
|
<<: *common
|
|
windows:
|
|
<<: *common
|