-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Rust: Move to bzlmod. #16716
Rust: Move to bzlmod. #16716
Conversation
This gets rid of our last workspace dependency. In particular, this change also gets rid of the checked-in extra lock files that took forever to generate.
This also bumps a bunch of external dependencies.
8177a9b
to
496fff4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hooray! 🎉
Build changes look sensible to me (but the Bazel upgrade seems like it might have broken something?).
We need an internal PR for this, as the path to the build targets change, otherwise I'm not aware that anything is broken. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! Looks good on the bazel side, with just a couple of comments that can be freely ignored
visibility = None, | ||
symbols_test = True, | ||
**kwargs): | ||
rust_label_name = name + "_single_arch" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wouldn't it be maybe better to use single_arch/name
, to get a consistent binary base name?
@@ -0,0 +1,23 @@ | |||
load("@rules_rust//rust:defs.bzl", "rust_binary") | |||
load("@semmle_code//buildutils-internal:glibc_symbols_check.bzl", "glibc_symbols_check") | |||
load("@semmle_code//buildutils-internal:lipo.bzl", "universal_binary") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not in the context of this PR, but we probably should think about moving this rule in this repo or go with the separate bazel lib repo idea we had
This gets rid of our last workspace dependency.
In particular, this change also gets rid of the checked-in extra
lock files that took forever to generate.
This PR also upgrades bazel to 7.2.0 while we're at it, and upgrades a bunch of external dependencies.