On Wed, Jul 22, 2020 at 4:02 PM John <
johns...@gmail.com> 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 = "path/to/my/proto";
>
>
>
> I use a script that finds all my proto files and the generates the go files by recursively moving through folders looking for .proto files.
>
> I then enter that directory and do:
>
> /usr/local/bin/protoc -I =./ ./name.proto --go_out=plugins=grpc:./ --proto_path=/home/user/go/src
Have you tried the --go_opt=paths=source_relative option?
>
> This works, however it doesn't generate the go files in that directory, it generates it inside the proto's directory with a directory structure like:
>
> ./path/to/my/proto/name.pb.go
>
> Where, what I want is:
>
> name.pb.go
>
> I've tired a bunch of different options, nothing seems to get me what I want.
>
> Anyone know where I'm going wrong here?
>
> Thanks!
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
golang-nuts...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/ad5c5812-37e3-4f84-bd1d-5fcfcc9cb28eo%40googlegroups.com.