Bzlmod local sysroot #1
Merged
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
kklochkov
force-pushed
the
bzlmod-local-sysroot
branch
from
02a35d8 to
a176324
Compare
kklochkov
force-pushed
the
bzlmod-local-sysroot
branch
from
a176324 to
5cca779
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.
The idea of the PR to expose locally installed
sysrootlibs (some libs might not have Bazel support or relatively time-consuming to bazelize for instanceSDL2) for consumption inBazel.The PR introduces
sysrootextension forbzlmod. The extension allows to explicitly to declare which libraries to expose toBazeldepending on a target platform.Another approach would be (removed in this PR) to use
use_repo_rule+new_local_repositoryonce bazelbuild/bazel#18285 is available.