-
Notifications
You must be signed in to change notification settings - Fork 1.6k
jsonpb/jsonpb_test_proto/test_objects.proto does not regenerate #149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sorry to be a bother, but I just wanted to remind you of this issue. |
Curious. Running What does |
I have protoc version 3 beta 2
On golang/protobuf tip
|
I have never used M before, but I would usually solve this problem by creating a google/protobuf folder, placing the proto files in there and then setting the appropriate proto_path |
I am on osx 10.10.5 with go1.6 |
any ideas? |
There's still got to be something different between our environments. I can't fix anything without being able to reproduce the problem you're seeing. Somehow my protoc is finding google/protobuf/duration.proto and friends without issue. Did you install protoc from source? That might be it, if those .proto files aren't included in binary distributions. |
I don't install from source it I can just install the osx version. I am lazy like that. I don't think this has anything to do with the fact that the proto files are compiled into protoc. |
Ok but this also does not work
|
Ah, if you don't have the source install then that'd be the problem. The "google/protobuf/duration.proto" is the official path for it, but it's a known problem for us that we don't have a global filesystem for everyone, and at least on my system the way that import is resolved is by looking at where the protoc sources are found. We don't want to make "github.com/golang/protobuf/ptypes/duration/duration.proto" be the official way that that .proto gets imported either. I think for now you'll need a proto source installation (you don't have to build it or anything, just have it unzipped somewhere) and point -I (or --proto_path) at its src directory. |
But this works
If I change the imports to
|
Why not just make a google/protobuf folder with all the .proto files and then you can have
And you can keep all your import paths. |
I mean this is going to be a problem for a lot of people? |
This is just #143 then. |
This is with commit 553c764
The same is happening on master.
The text was updated successfully, but these errors were encountered: