-
-
Notifications
You must be signed in to change notification settings - Fork 676
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
Support using precompiled protoc binaries #2902
Comments
I think improving As a side note, since |
Thanks for your response. I can try to have a look. My fist guess would be that if we are lucky wrapping some dependencies in a bzl file with a |
I can tell you that my project already uses the precompiled |
That sounds great. How exactly did you set it up? I did a similar thing like described here: bazelbuild/rules_proto#36 (comment). I can share my exact changes tomorrow. |
@achew22 thanks for your responses. I tried it again. I don't know what I did wrong before, but now it is working: kubevirt/kubevirt#5959 |
What version of rules_go are you using?
v0.27
What version of gazelle are you using?
v0.23
What version of Bazel are you using?
3.7.2
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
Any other potentially useful information about your toolchain?
What did you do?
When switching locally branches in a project which
rules_go
we spend quite some time recompilingprotoc
over and over.What did you expect to see?
It would be great if
rules_go
could work with precompiled protoc versions, like described in bazelbuild/rules_proto#36 and for example implemented at bazelbuild/rules_scala#1142 for the scala rules.What did you see instead?
protoc
gets compiled every time we switch a branch.The text was updated successfully, but these errors were encountered: