You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,6 +165,23 @@ If you import `rules_rust` via this extension, existing `load("@rules_rust//..."
165
165
Using this extension is STRONGLY ENCOURAGED because it carries fixes that improve Windows behavior, rust-analyzer integration, and related compatibility work.
166
166
In addition, when using the `rules_rs` toolchains, loading the compilation rules from `@rules_rs` directly and using the extension is REQUIRED for toolchain resolution to work correctly, at least until https://github.com/bazelbuild/rules_rust/pull/3857 is accepted by rules_rust maintainers. See the Migration section for more info.
167
167
168
+
## Import `rules_rust_prost` from `rules_rs`
169
+
170
+
`rules_rs` also exports a `rules_rust_prost` module extension for the prost integration:
The default prost toolchain and its cargo dependencies are provided by `rules_rs`. If you need different prost, tonic, or plugin versions, you can still define your own `rust_prost_toolchain` from `@rules_rust_prost//:defs.bzl`.
184
+
168
185
## Platform Configuration
169
186
170
187
For reliable toolchain resolution, ABI choices should be explicit on every platform participating in your build, including the host platform.
0 commit comments