-
-
Notifications
You must be signed in to change notification settings - Fork 661
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
go_proto_compiler: integration with proto_lang_toolchain #2684
Comments
There's no way to do that at the moment. It looks like |
Hi @jayconrod Thank you for answering. I'd like to help with this, but I have no idea where to begin. Where should I start looking to add support for |
Sorry, this needs more experimentation and design before there's an implementation plan, and I don't have bandwidth to do that right now. |
Hey @jayconrod, how can we move forward this issue? I'd like to see this solved, and can definitely give a hand here. |
Sorry, I have zero bandwidth to work on this or review changes here. |
@jayconrod understandable. Can you pull in someone else that can help out here? |
cc @bazelbuild/go-maintainers if anyone's interested in looking at this. |
Ideally, this should work with Bazel's |
What version of rules_go are you using?
v0.20.1
What version of gazelle are you using?
0.18.2
What version of Bazel are you using?
3.6.0
Does this issue reproduce with the latest releases of all the above?
Not applicable
What operating system and processor architecture are you using?
Linux x86)64
Any other potentially useful information about your toolchain?
Not applicable
What did you do?
This is more a question related to #2489.
I was able to fix the issue reported there, but I want to use pre-built binaries just like this instead of compiling protobuf. Is there a way to do that?
What did you expect to see?
Not applicable
What did you see instead?
Not applicable
The text was updated successfully, but these errors were encountered: