Damien Neil

https://developers.google.com/protocol-buffers/docs/reference/go-generated#package As the error says, you need to specify the import path of the Go package containing the `.proto` file. The simplest way to do this is with a `go_package`...

> Is there a way to output the code /tmp/proto/test.pb.go? Pass `--go_opt=paths=source_relative` to `protoc`. See: https://developers.google.com/protocol-buffers/docs/reference/go-generated#invocation

You need to provide the option to both plugins: `--go-grpc_opt=paths=source_relative`.

> I think --go_opt=paths=source_relative should be the default. Unfortunately impossible to change without breaking existing users. Also, I strongly suspect `--go_opt=module=` is better for most cases these days.

@myitcv Hard to say without know without knowing what the point is. What vgo-related issues do you see? FWIW, I've been happily using vgo with the protobuf repo for a...

@myitcv My take is that there are two broad ways in which protocol buffers are used to build programs. One is with full support of the build system. When building...

Multiple registration is definitely a problem. I agree with @rsc that vgo should make the situation better than it was before. With vendoring, it's easy for a single generated proto...

We did not, alas. This is, unfortunately, quite difficult to fix. The problem is that we generate each file in a package independently from every other file in the package....

C++ has the advantage that the protobuf language and its namespace rules map precisely onto C++. I believe `import public` in C++ just means "put a `#include` in the `.pb.h`...

Java might be the more interesting case.