| commit | 33fdddd03c9a958d82efcf9658f9dce13a9f06df | [log] [tgz] |
|---|---|---|
| author | Cameron Martin <cameronmartin123@gmail.com> | Fri Feb 23 12:55:58 2024 +0000 |
| committer | GitHub <noreply@github.com> | Fri Feb 23 12:55:58 2024 +0000 |
| tree | 48677317d862a33b5551815c0c721d71c790294d | |
| parent | 0e0241e9b0e4122f1e28a1ca0d358dd987f21971 [diff] |
Fix bzlmod examples on windows (#2454) On windows (and some other platforms), the file extension of cargo, rustc, etc have an extension. The module extension for loading crates did not take this into account, causing it to error on windows. Additionally, when using bzlmod to build vendored crates, the runfiles tree would exceed the 260 char windows path limit. To mitigate this, I have shortened the internal_deps module extension to just `i` and changed the build script suffix to `_bs` from `_build_script`. This makes the path names below the 260 char limit. This makes the bzlmod CI run on windows, to avoid regressing this. Currently gen_rust_project does not run on windows for other reasons, although we do build this.
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.