Skip to content

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

Closed
AdreKiseque opened this issue Oct 1, 2024 · 6 comments
Closed

Comments

@AdreKiseque
Copy link

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

@AdreKiseque AdreKiseque changed the title Install with Visual Studio Built Tools instead of Visual Studio Community Install with Visual Studio Build Tools instead of Visual Studio Community Oct 1, 2024
@ChrisDenton
Copy link
Member

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.

@djc
Copy link
Contributor

djc commented Oct 1, 2024

I guess for those users who do have a license, it might be nice to offer the option?

@ChrisDenton
Copy link
Member

Sure, it could be an option.

@AdreKiseque
Copy link
Author

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.

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.

@ChrisDenton
Copy link
Member

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.

@AdreKiseque
Copy link
Author

I see. What an unfortunate inconvenience.

@djc djc reopened this Oct 1, 2024
@djc djc closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants