Skip to content
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

Installation of Visual Studio tools is not well integrated #1114

Closed
kornelski opened this issue May 12, 2017 · 2 comments
Closed

Installation of Visual Studio tools is not well integrated #1114

kornelski opened this issue May 12, 2017 · 2 comments

Comments

@kornelski
Copy link
Contributor

When installing Rust on Windows for the first time there's a wall of text, including a message saying that Visual Studio tools needs to be installed.

  • Wall of text is not a nice experience, and if you don't read it, you get worse setup.
  • It's a completely manual step.
  • Copying of the URL from console is a bit cumbersome.

I'd prefer if Rustup had an option to at least automatically open the VS download URL. It could be the first option when user presses Enter, so user would be guided towards best solution even if they don't read the instructions.

If #253 is integrated, it'd be nice if VS install was a step in the installer.

@ctaggart
Copy link

The current installer prints this:

image

In my case, I have Visual Studio 2017 already installed. It would be nice if rust-init.exe launched or made it easy to launch a script that installed the required dependencies.

@rami3l
Copy link
Member

rami3l commented Jun 10, 2024

It seems to me that this has been fixed.

As described in https://github.com/rust-lang/rustup/blob/81a71647f4615d85267325b8dd8019a37e01f9fd/doc/user-guide/src/installation/windows-msvc.md, Rustup will now offer to install VS C++ build tools automatically (since #2954).

Also, the page above provides a rather detailed list of steps to follow if you'd like to install these tools manually.

Please feel free to reopen if you believe that is not the case.

@rami3l rami3l closed this as completed Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants