[FR]: How does gRPC generation work?

[antspy]

What is the current behavior?

Hi,

I am using this toolchain to compile protos without having to compile protoc from scratch, which makes a ton of sense.

Now I am trying to also add gRPC generation to my proto files. I tried using python macros from rules_proto_grpc or from the main grpc repo itself, but in both cases, it seems like they are trying to rebuild protoc or grpc, and my builds fail because I have set the following in my .bazelrc:

common --per_file_copt=external/.*protobuf.*@--PROTOBUF_WAS_NOT_SUPPOSED_TO_BE_BUILT
common --host_per_file_copt=external/.*protobuf.*@--PROTOBUF_WAS_NOT_SUPPOSED_TO_BE_BUILT
common --per_file_copt=external/.*grpc.*@--GRPC_WAS_NOT_SUPPOSED_TO_BE_BUILT
common --host_per_file_copt=external/.*grpc.*@--GRPC_WAS_NOT_SUPPOSED_TO_BE_BUILT
common --incompatible_enable_proto_toolchain_resolution

Describe the feature

Is there a way to also call grpc in the same way?

If not, how are you supposed to get around the GRPC_WAS_NOT_SUPPOSED_TO_BE_BUILT flag? Using which macros / toolchains?

An example / pointer would be much appreciated! Thank you :)

[ramilmsh]

I'm having the same issue generating python and dart grpc code via rules_proto_grpc's proto_plugin

@antspy i suspect you could try following this article with an associated repo

it claims to solve the grpc issue and while the solution is for python, i don't see why it wouldn't work in general. Main idea being that you use prebuilt protoc from grpc-io for grpc rules. I don't understand how exactly the toolchain discovery works, however, so i was not successful. i hope you have more luck

[antspy]

@ramilmsh There is a WIP PR: #58

It doesn't seem to be ready yet, I don't understand the code enough to see what's missing, but perhaps it's helpful.

I ended up calling protoc compiler directly in my scripts. It's not very bazel friendly but for now it will do