Compile protos from multiple packages #42
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an issue report in the form of a PR (to ease demonstration). The primary changes reside in the second commit.
It seems to be not possible to generate go code for multiple packages (in multiple invocations of protoc, even), when dependencies exist between those packages.
Using
import_prefix
to prepend the relative path from$GOPATH/src
won't work because the protobuf import itself will no longer be valid. Using the fully-qualified go import path in the protos themselves will break compilation in other languages where the directory structure required by thego
tool isn't necessarily present. Is there a standard way to address this?Here's the actual failure: