-
Notifications
You must be signed in to change notification settings - Fork 282
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
no matching toolchains found for types @io_bazel_rules_scala//scala_proto:toolchain_type #768
Comments
You need to set up a toolchain. There is some documentation here: |
I did attempt to do that but it doesn't seem to be working: |
So I tried reworking things with the other rules_scala and hit the same problem. After some fumbling around and reading the Bazel docs on toolchains I realized that toolchains need to be registered in |
The solution that worked for me was to add this to
It'd be great if the docs mentioned this! |
Any chance you can send a PR to the docs?
…On Fri, Jun 14, 2019 at 3:11 AM Ted Mielczarek ***@***.***> wrote:
The solution that worked for me was to add this to WORKSPACE:
***@***.***_bazel_rules_scala//scala_proto:toolchains.bzl", "scala_proto_register_toolchains")
scala_proto_register_toolchains()
It'd be great if the docs mentioned this!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#768?email_source=notifications&email_token=AAKQQF52HAYU7YEHV7UKHOLP2LO3LA5CNFSM4HXNXGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXVLT3Q#issuecomment-501922286>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKQQF2DDH43UBDSGHALY4TP2LO3LANCNFSM4HXNXGAA>
.
|
I'm having an issue using
scalapb_proto_library
. I've built a simple reduced testcase project here: https://github.com/luser/bazel-scala-proto-testI'm using bazel 0.26.1:
The error is:
I am very new to Bazel and I'm also not incredibly up-to-speed on Scala so it's possible I'm just doing something wrong, but I'd appreciate any help!
The text was updated successfully, but these errors were encountered: