rules_proto icon indicating copy to clipboard operation
rules_proto copied to clipboard

Protocol buffer rules for Bazel

Results 27 rules_proto issues
Sort by recently updated
recently updated
newest added

Many tools require us to specify other versions of `protoc` than the default that comes with the ruleset, and it would be really nice to be able to specify that...

P3

Instead of maintaining a list of protobuf dependencies rules_proto should use the provided bzl file.

P3

Hello, I encounterred really odd issue, and stucked for a couple of days. Could someone help? https://stackoverflow.com/questions/73254664/bazel-build-failed-cannot-open-include-file-google-protobuf-text-format-h

P4

my project import rules_proto and grpc, when I cross compile for arm with with --incompatible_enable_cc_toolchain_resolution and --platforms, it generated protoc.exe for arm, so protoc.exe cannot executed on build host( x86_64...

P4

i.e. the equivalent of `protoc --encode=$MESSAGETYPE`. This is useful when embedding binary protos in applications. Something like: ``` proto_encode( name = "encoded", src = "something.textproto", message = "foo.bar.ThingProto", deps =...

P4

I would like to have some way to tell `rules_proto` "please recompile protoc". I came upon this while trying to use rules_proto on nixos, which doesn't have ld in /lib64/ld-linux-x86-64.so.2,...

P4

Released `protoc` binaries are great. It saves a lot of build time. Thanks for doing this! However, maybe this could be extracted to a separate repository? If I have to...

P3

Alternative proto rulesets (namely [stackb](https://github.com/stackb/rules_proto/tree/master/java#java_proto_library)) support not generating Java byte code for `proto_library.deps()` via a `transitive` attribute. Today, `java_proto_library` generates bytecode for both a `proto_library`'s `srcs` and `deps` attributes. Generating...

P4

I'm wondering how to write and use new `proto_lang_toolchain`s. Are there any examples or a design doc? Related: - https://github.com/bazelbuild/rules_go/issues/2266 - https://github.com/grpc-ecosystem/grpc-gateway/issues/1094#issuecomment-562910981

documentation
question
P3

Is there a way to enforce that every `proto_library` target are compiled with `--fatal_warnings`? For reference, this flag was added [here](https://github.com/protocolbuffers/protobuf/pull/8131), and causes the compilation to fail if a warning...

question
P4