We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently rules_rust requires the user to override the protoc compiler
rules_rust/proto/protobuf/toolchain.bzl
Line 174 in df7a655
However Bazel 7 introduced --incompatible_enable_proto_toolchain_resolution and rules_proto 6.0 allows users to register a toolchain for protoc. The toolchain_type is @rules_proto//proto:toolchain_type: https://github.com/bazelbuild/rules_proto/blob/6.0.0-rc3/proto/BUILD#L57-L60
--incompatible_enable_proto_toolchain_resolution
toolchain_type
@rules_proto//proto:toolchain_type
https://registry.bazel.build/modules/toolchains_protoc is a reference implementation and has examples
Similar change in other language rules:
The text was updated successfully, but these errors were encountered:
@UebelAndre maybe? Is this something that would be welcome in rules_rust to help avoid protoc compilation times for rust users?
Sorry, something went wrong.
I would happily review a PR adding this support :)
Hey! It'd definitely be welcome! 😄
illicitonion
No branches or pull requests
Currently rules_rust requires the user to override the protoc compiler
rules_rust/proto/protobuf/toolchain.bzl
Line 174 in df7a655
with a fixed label to replace it.
However Bazel 7 introduced
--incompatible_enable_proto_toolchain_resolution
and rules_proto 6.0 allows users to register a toolchain for protoc. Thetoolchain_type
is@rules_proto//proto:toolchain_type
: https://github.com/bazelbuild/rules_proto/blob/6.0.0-rc3/proto/BUILD#L57-L60https://registry.bazel.build/modules/toolchains_protoc is a reference implementation and has examples
Similar change in other language rules:
The text was updated successfully, but these errors were encountered: