Update rules_cc to 0.2.14. #605
Merged
+15
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
helly25
requested review from
dzbarsky,
fmeum,
jsharpe and
rrbutani
as code owners
…kspace to work (false/true and true/false) already worked but (true/true) failed in bazel 8 before this.
… not part of trunk checks).
fmeum
approved these changes
Nov 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With newer versions of
rules_ccfor WORKSPACE setups we need the following new flag that has to be put into the relevant .bazelrc files:common --repositories_without_autoloads=cc_compatibility_proxy.We also need a main
WORKSPACE.bzlmodin order for--enable_bzlmod --enable_workspaceto work (false/true and true/false) already worked but (true/true) failed in Bazel 8 before this.