Skip to content
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

Merged
merged 4 commits into from
Jun 11, 2024
Merged

Rust: Move to bzlmod. #16716

merged 4 commits into from
Jun 11, 2024

Conversation

criemen
Copy link
Collaborator

@criemen criemen commented Jun 10, 2024

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.

criemen added 3 commits June 10, 2024 17:03
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.
@criemen criemen added the depends on internal PR This PR should only be merged in sync with an internal Semmle PR label Jun 10, 2024
@criemen criemen force-pushed the criemen/rust-bzlmod-new branch from 8177a9b to 496fff4 Compare June 10, 2024 15:04
@criemen criemen marked this pull request as ready for review June 10, 2024 15:34
@criemen criemen requested review from a team as code owners June 10, 2024 15:34
Copy link
Contributor

@tausbn tausbn left a 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?).

@criemen
Copy link
Collaborator Author

criemen commented Jun 10, 2024

We need an internal PR for this, as the path to the build targets change, otherwise I'm not aware that anything is broken.
But I see the backlink to this PR is missing, let me fix that.

Copy link
Contributor

@redsun82 redsun82 left a 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"
Copy link
Contributor

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")
Copy link
Contributor

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

@criemen criemen merged commit 3574b9f into main Jun 11, 2024
36 of 43 checks passed
@criemen criemen deleted the criemen/rust-bzlmod-new branch June 11, 2024 11:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C# depends on internal PR This PR should only be merged in sync with an internal Semmle PR JS Python Ruby
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants