-
Notifications
You must be signed in to change notification settings - Fork 82
Install protoc locally in the source tree #232
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
Conversation
bf974f8
to
450ec95
Compare
@marquiz I think this would be good, especially if it helps us avoiding to force dockerized protobuilds on ourselves and everybody else in a local development workflow. One related question though. Since our |
450ec95
to
4dfced7
Compare
Yeah, sure, I can try :) As soon as I get this working (i.e. make the ci pass muster). One gap still remains that we don't check the protoc (or plugins) versions installed in the source tree. |
Now I got it working locally, too. Was just a stupid user error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you !
4dfced7
to
6528705
Compare
@klihub updated. Check it. The build from source case was broken in the previous version. I hope I got it right... |
Install (and use) protoc and plugins under build/tools in the source tree in an attempt to ensure that the correct version of the tooling is always used. Signed-off-by: Markus Lehtonen <[email protected]>
6528705
to
2394daa
Compare
Thanks @klihub for the review. One possible change I had in mind is: -INSTALL_DIR="$PWD/build/tools"
+PROTOC_DIR="$PWD/build/protoc" That would make it completely wipe/clean protoc and deps e.g. in case of version bumps. Thoughts? |
@marquiz Sorry, you lost me there... I think. So instead of installing |
It's like |
Install (and use) protoc and plugins under build/tools in the source tree in an attempt to ensure that the correct version of the tooling is always used.