-
Notifications
You must be signed in to change notification settings - Fork 911
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
Allow +toolchain
for rustup
#1498
Comments
CC #1489. |
In addition to
Also |
I would like to do this. I noticed that |
Hi @pickfire, friendly note that from this comment from #1489, I started working on the 2nd PR for +foo variant in the same scope of #2031. Should be able to push an update later today for +foo variant. |
@BeniCheni Yeah, but that's just for |
@pickfire, from this comment from #1489:
From my comment there, I indicated my interest in working on #1498 here. But I'm happy to share, if you want to try out a PR for #1498 here. Let me know if you are committed to this issue. If yes, I can check out other open issues. If no, I will continue to pick up this issue, since #2031 is in final shape. |
It was surprising to me that I couldn't use the
+nightly
parameter on rustup for adding thewasm32-unknown-unknown
target to nightly:(and other combinations didn't work either). Instead I had to find the
--toolchain
parameter ofrustup target add
. It would be nice if+nightly
would work onrustup
, too.The text was updated successfully, but these errors were encountered: