-
Notifications
You must be signed in to change notification settings - Fork 0
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
build-protobufs now requires full protoc install #2
Comments
@tgross I can't build build protobufs right now as I'm on the road w/ this change. |
J. Random Passerby Developer isn't going to be building the protobufs though, are they? That's going to be something that only someone creating new language bindings is going to do.
We're not messing with anyone's PATH. The directions in the
The primary con was that it assumed you had a GOPATH set, which isn't going to be the case by default. The fallback GOPATH ( |
Sure you can: add the directory where you have |
Looks like
plan-core/build-protobufs.h
assumes that protoc is in the user's PATH. it used to be set up to not do this at all at this level and not require a person to do this (and just follow the instructions that were on the protobuf pages). My vision was that it was easy for visitors to build protobufs rather than do a full-blown protoc install. Does it make sense to only throw the protoc not found message ifGrpc.Tools/...
also can't be found? I don't want to have to mess w/ ppl's PATH just for them to build protobufs and now I'm left unable to build them on machines that don't have a full protoc install. Not getting the cons of the previous system.The text was updated successfully, but these errors were encountered: