commit | fc601ba32f21ec034baebc487646dea92afbcd04 | [log] [tgz] |
---|---|---|
author | Eric McBride <ericmcbridedeveloper@gmail.com> | Tue Mar 26 12:11:50 2024 -0500 |
committer | GitHub <noreply@github.com> | Tue Mar 26 17:11:50 2024 +0000 |
tree | 76a6a8703d1a1721442e989538f1bf2e9f6f00fe | |
parent | 98fab85a713a67e804a299dfe57a02deb9790ca1 [diff] |
Fix cargo-bazel recompile for MODULE.bazel (#2570) - Addresses https://github.com/bazelbuild/rules_rust/issues/2531 - Wrote a function, thats basically copy / pasted from `crates_universe/private/generate_utils.bzl` to account for the `module_ctx` Can probably make the original function more generic if thats more desired. I'm not sure if the maintainers would prefer a one off, since the `MODULE.bazel `feature set for `crates_universe` isn't exactly "Stable" yet. - Noticed theres no way to "bootstrap" the new `cargo` features in `MODULE.bazel` , like you can for `crates_universe`. May need to open an issue for this. Tested by using the `CARGO_BAZEL_GENERATOR_URL` and `CARGO_BAZEL_GENERATOR_SHA256` environmentals. This looks to cause some failing unit tests. Not sure how to get support on this - Failsafe of using the cargo buildstrap `cargo-bazel` if no URLs are found, and if theres no environmentals. --------- Co-authored-by: UebelAndre <github@uebelandre.com>
This repository provides rules for building Rust projects with Bazel.
General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust
.
Please refer to the full documentation.