Closed fmeum closed 1 year ago
~Stacked on #163 to get the tests to pass - the diverged toolchain definitions did not contain the correct compiler names.~
@oquenchil No longer stacked.
@buildbreaker2021 The automated release to the Bazel Central Registry didn't work. Quoting @kormide:
Hey, it's because buildbreaker2021 published the release but they don't have a fork of bazel-central-registry with the app installed on it. It wasn't able to send them an email because their email isn't listed publicly on their github profile.
Yes I am aware of that will try to push it to central registry manually today.
As of Bazel 6.0.0, all Bazel-provided toolchains report consistent compiler names that can be matched on with
select
. Having a central place forconfig_setting
s that can be used for this purpose makes it so that rulesets don't have to define them themselves and moving the compiler flag out of@bazel_tools
becomes easier as it is no longer referenced directly.Fixes https://github.com/bazelbuild/bazel/issues/14914