-
Notifications
You must be signed in to change notification settings - Fork 903
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
[Windows] rustup-init.exe's on-screen instructions could be better #1363
Comments
An illustrated guide (2018-03-02)
|
@shepmaster Awesome guide. But these steps also show how much FWIW, I also think this change from 2015 to 2017 did not change in the last weeks because I already tried the same step 2, 3 montns ago and then I already had this "which version is right?" confusion and cancelled the whole thing. I think this is something the rust team might want to fix before the big Rust 2018 release. |
A caveat to these instructions: |
I wanted to install rust in order to do
cargo install <various-tools>
. I see few issues here when gettings started:The on-screen instructions talk about version 2015 but the site where one should download says 2017. This confused me while searching for the right version:

The site where one downloads is full of text and clutter and various download options. Took me a few moments to read the page and find the right software to download and install.
Then I tried
ruseup-init.exe
again, but it still complained about about missingC++ build tools
. Turns out that the software bundle installed in step 2 does not by default install theC++ build tools
. So back to theBuild Tools for Visual Studio 2017
and checking the right extra checkbox and reinstall.Step 2 and 3 take about 2-3 hours and lots of disk space.
Actionable things that could be better here to improve Onboarding:
Related to #1122.
PS As a side note I already tried to install some weeks ago and stopped at step 2 then noticing that I had not enought disk space.
The text was updated successfully, but these errors were encountered: