-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Bazel 7.3.1 (bzlmod) #51
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Hello, thank you for this wonderful change, we are planning to update the repo to use Bzlmod, and due to some technicalities of how we are exporting code, it is much easier for us to create a separate commitment. Would you mind if we used this PR as a reference? We can add a credit to you in the README |
@karnseth, sure that's fine! I'll be happy that I don't have to maintain my fork :) |
Committed at a00b422 Thank you! |
Updates the Bazel toolchain dependencies to their latest versions and migrates away from the previous Bazel
WORKSPACE
in favor of BzlmodMODULE.bazel
Doesn't quite fix #46, because it's not published to the Bazel Central Registry, but you can import into other Bzlmod MODULES by doing something like:
Also fixes a
.bazelrc
duplicate declaration:build --host_cxxopt='-std=c++17'
->test --host_cxxopt='-std=c++17'
I do not think the previous version had a working wheel or it may have been a WIP. This PR doesn't fix the python gaps, but it at least makes it conformant to the latest rules.