Provide Bazel 8 compatibility #169
Merged
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
martin4861
force-pushed
the
martin4861/provide-bazel-8-compatibility
branch
from
528fe24 to
3701462
Compare
sbmueller
approved these changes
Aug 4, 2025
martin4861
added a commit
that referenced
this pull request
Aug 6, 2025
Follow up on #169 In order to use Bazel 8 following changes are needed: * select proper `sysroot`s for some additional toolchains * `+` instead of `~` as `bzl_mod` path seperator (backwards compatibility to Bazel 7 can be achieved using `--incompatible_use_plus_in_repo_names`) for some more toolchains Tested in - [x] starling-core (Bazel 6) - [x] starling-core (Bazel 7) - [x] starling-core (Bazel 8)
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.
In order to use Bazel 8 following changes are needed:
globsare markedallow_empty+instead of~asbzl_modpath seperator (backwards compatibility to Bazel 7 can be achieved using--incompatible_use_plus_in_repo_names)Tested in