Repository navigation
Migrate to injectable warning features in score_bazel_cpp_toolchains #519
Description
What
Migrate Baselibs to the newest score_bazel_cpp_toolchains and use the injectable warning features introduced in score_cpp_policies#33 for the GCC and LLVM toolchains.
This centralizes warning policy configuration, keeps both toolchains aligned, and lets Baselibs benefit from shared policy updates.
Toolchain configuration
Inject selectable warning features with extra_known_features and default-enabled warning features with extra_enabled_features in each toolchain configuration.
Acceptance Criteria (DoD)
- Baselibs uses the newest compatible
score_bazel_cpp_toolchainsversion. - The GCC toolchain uses the injectable warning features from
score_cpp_policies. - The LLVM toolchain uses the injectable warning features from
score_cpp_policies.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
ian-harmon-traton commentedon Aug 26, 2026
Created #524 to address this
bazel: migrate warnings and sanitizers to score_cpp_policies features
bazel: migrate warnings and sanitizers to score_cpp_policies features
bazel: migrate warnings and sanitizers to score_cpp_policies features
bazel: migrate warnings and sanitizers to score_cpp_policies features
bazel: migrate warnings and sanitizers to score_cpp_policies features
Use the score_coverage 0.3.0 release
bazel: migrate warnings and sanitizers to score_cpp_policies features
bazel: migrate warnings and sanitizers to score_cpp_policies features
bazel: migrate warnings and sanitizers to score_cpp_policies features
Use the score_coverage 0.3.0 release
bazel: migrate warnings and sanitizers to score_cpp_policies features