Update reference to rules_cc to main.zip. This is required by https://github.com/bazelbuild/rules_cc/issues/107 #1604
Conversation
This file contains 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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
test_382544881
branch
2 times, most recently
from
8eca65f
to
366a6a5
Compare
…ild/rules_cc#107 The longer term solution is: - To use a named release of rules_cc once that is available (See bazelbuild/rules_cc#91) - Wrap the `http_archive` rules with `maybe` so that there will not be conflicts if downstream users try to mix rules_cc versions. PiperOrigin-RevId: 382555074
copybara-service
bot
force-pushed
the
test_382544881
branch
from
366a6a5
to
d2527c2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update reference to rules_cc to main.zip. This is required by bazelbuild/rules_cc#107
The longer term solution is:
http_archiverules withmaybeso that there will not be conflicts if downstream users try to mix rules_cc versions.