On Wed, Jul 22, 2020 at 4:32 PM John wrote:
>
> Mathew + Burak,
>
> That was it.
>
> Out of curiosity, where did you find that option. I didn't see it in
> protoc's help. google search for "protoc --go_opt" did not yield good
> results. It did find:
Mathew + Burak,
That was it.
Out of curiosity, where did you find that option. I didn't see it in
protoc's help. google search for "protoc --go_opt" did not yield good
results. It did find: https://grpc.io/docs/languages/go/quickstart/, but
I'd like to bookmark the definite list if you
John,
On Wed, 22 Jul 2020 at 23:02, John wrote:
> I then enter that directory and do:
>
> /usr/local/bin/protoc -I =./ ./name.proto --go_out=plugins=grpc:./
> --proto_path=/home/user/go/src
>
> This works, however it doesn't generate the go files in that directory, it
> generates it inside the
On Wed, Jul 22, 2020 at 4:02 PM John wrote:
>
> In essence, I'm switching over to the new go protocol buffer lib and protoc
> libraries.
>
> In the new version, you are told to specify go_package option in the .proto
> file. So I updated all mine to have that:
>
> go_package =
In essence, I'm switching over to the new go protocol buffer lib and protoc
libraries.
In the new version, you are told to specify go_package option in the .proto
file. So I updated all mine to have that:
go_package = "path/to/my/proto";
I use a script that finds all my proto files and the
