Bazel module builds #1224
Merged
Bazel module builds #1224
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
stonier
force-pushed
the
release/0.8.0-1
branch
from
aee1bc4
to
0ed499b
Compare
jbeder
approved these changes
Sep 17, 2023
This was referenced Sep 18, 2023
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.
This paves the way for a bazel build, module style (with the goal of then publishing it on the bazel-central-registry).
MODULE.bazelwith package and dependency information.bazelignoreignoring the locally downloaded gtest in favour of a module depended oneNB: The traditional means of bazel building coexists side-by-side, i.e. uses
WORKSPACEfor it's dependencies and no--enable_bzlmodflag.