Arch Linux User Repository

@vitaliikuzhdin Thanks for your feedback.

@brody, this definitely requires at least protobuf. The nature of all the protoc-gen-* Go packages is that they are not used directly but are called by protoc (provided by the protobuf package). The first line of the upstream URL clearly says:

gRPC-Gateway is a plugin of protoc.

You can also confirm this by running the binary itself:

$ protoc-gen-grpc-gateway something
protoc-gen-grpc-gateway: unknown argument "something" (this program should be run by protoc, not directly)

As for protoc-gen-go and protoc-gen-go-grpc, the same logic of nested plugin support applies:

protoc \                 # <-- requires protobuf
  --go_out=. \           # <-- requires protoc-gen-go
  --go-grpc_out=. \      # <-- requires protoc-gen-go-grpc
  --grpc-gateway_out=. \ # <-- requires protoc-gen-grpc-gateway (grpc-gateway)
  your_service.proto

The same is stated in the project's README.md:

Install by running

go install \

github.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-grpc-gateway \

github.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-openapiv2 \

google.golang.org/protobuf/cmd/protoc-gen-go \

google.golang.org/grpc/cmd/protoc-gen-go-grpc

This will place four binaries in your $GOBIN:

• protoc-gen-grpc-gateway
• protoc-gen-openapiv2
• protoc-gen-go
• protoc-gen-go-grpc

The same as for the package protoc-gen-go-grpc. I see no reason why grpc-gateway should be dependent on protoc-gen-go, protoc-gen-go-grpc resp. protobuf. Or am I missing something?