-
Notifications
You must be signed in to change notification settings - Fork 941
Install with Visual Studio Build Tools instead of Visual Studio Community #4038
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
Comments
Build tools requires the user (or organization) has a license for Community, Professional or Enterprise. Installing Community is the only way to get a free license. |
I guess for those users who do have a license, it might be nice to offer the option? |
Sure, it could be an option. |
Oh, that's bizarre. It doesn't let you install Build Tools without first obtaining a license that's free and automatic with another installation? I'd have to take your word for it, since I've never encountered any sort of barrier but probably had the license associated with my account to have me covered. If it really is like that I suppose it explains the current state of things. |
The barrier is "the license terms". This was brought up in 2022 so it's still an issue unless Visual Studio's licensing has changed in this area. |
I see. What an unfortunate inconvenience. |
Problem you are trying to solve
When Rustup doesn't detect the C linker tool things it needs, it prompts the user to install them through Visual Studio, launching the wizard primed to install the IDE with the necessary dependancies.
Solution you'd like
Rustup should instead have the wizard install Build Tools for Visual Studio, which can provide the dependancies without the overhead of the full IDE.
Notes
No response
The text was updated successfully, but these errors were encountered: