Which “Individual Component” from the Visual Studio installer is suitable for Rust development?
I have a fully updated install of Visual Studio Enterprise 2017 (currently 15.9.2) on my machine, and I want to do some Rust coding. The Rust installer tells me to install "Visual C++" build tooling, but I can't seem to figure out which one is needed.
That is, I tried installing "VC++ 2017 version 15.9 v14.16", but when I do cargo run on my hello world application, it halts with a message:
error: linker
link.exenot found
I don't want to go rampant and install all the C++ components in the installer, just the one I need. I'd prefer to install it as part of the Visual Studio installer, if possible.
Which "Individual Component" in the Visual Studio installer do I need for Rust?
Here's what's currently checked:
As a workaround, I was advised to run rustup default stable-x86_64-pc-windows-gnu which at least allows me to run the hello world example. (Or perhaps this is in fact a proper solution even?)
visual-studio rust
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
add a comment |
I have a fully updated install of Visual Studio Enterprise 2017 (currently 15.9.2) on my machine, and I want to do some Rust coding. The Rust installer tells me to install "Visual C++" build tooling, but I can't seem to figure out which one is needed.
That is, I tried installing "VC++ 2017 version 15.9 v14.16", but when I do cargo run on my hello world application, it halts with a message:
error: linker
link.exenot found
I don't want to go rampant and install all the C++ components in the installer, just the one I need. I'd prefer to install it as part of the Visual Studio installer, if possible.
Which "Individual Component" in the Visual Studio installer do I need for Rust?
Here's what's currently checked:
As a workaround, I was advised to run rustup default stable-x86_64-pc-windows-gnu which at least allows me to run the hello world example. (Or perhaps this is in fact a proper solution even?)
visual-studio rust
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
Have you verified, that your link.exe is in yourPATH? users.rust-lang.org/t/problems-with-installing-rust-on-windows/…
– hellow
Nov 26 '18 at 10:55
No, I had not, but have just checked and "The term 'link.exe' is not recognized..." if I try to invoke it.
– Jeroen
Nov 26 '18 at 11:10
add a comment |
I have a fully updated install of Visual Studio Enterprise 2017 (currently 15.9.2) on my machine, and I want to do some Rust coding. The Rust installer tells me to install "Visual C++" build tooling, but I can't seem to figure out which one is needed.
That is, I tried installing "VC++ 2017 version 15.9 v14.16", but when I do cargo run on my hello world application, it halts with a message:
error: linker
link.exenot found
I don't want to go rampant and install all the C++ components in the installer, just the one I need. I'd prefer to install it as part of the Visual Studio installer, if possible.
Which "Individual Component" in the Visual Studio installer do I need for Rust?
Here's what's currently checked:
As a workaround, I was advised to run rustup default stable-x86_64-pc-windows-gnu which at least allows me to run the hello world example. (Or perhaps this is in fact a proper solution even?)
visual-studio rust
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
I have a fully updated install of Visual Studio Enterprise 2017 (currently 15.9.2) on my machine, and I want to do some Rust coding. The Rust installer tells me to install "Visual C++" build tooling, but I can't seem to figure out which one is needed.
That is, I tried installing "VC++ 2017 version 15.9 v14.16", but when I do cargo run on my hello world application, it halts with a message:
error: linker
link.exenot found
I don't want to go rampant and install all the C++ components in the installer, just the one I need. I'd prefer to install it as part of the Visual Studio installer, if possible.
Which "Individual Component" in the Visual Studio installer do I need for Rust?
Here's what's currently checked:
As a workaround, I was advised to run rustup default stable-x86_64-pc-windows-gnu which at least allows me to run the hello world example. (Or perhaps this is in fact a proper solution even?)
visual-studio rust
visual-studio rust
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
edited Nov 26 '18 at 10:54
Jeroen
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
asked Nov 26 '18 at 10:36
JeroenJeroen
36.7k24130211
36.7k24130211
Have you verified, that your link.exe is in yourPATH? users.rust-lang.org/t/problems-with-installing-rust-on-windows/…
– hellow
Nov 26 '18 at 10:55
No, I had not, but have just checked and "The term 'link.exe' is not recognized..." if I try to invoke it.
– Jeroen
Nov 26 '18 at 11:10
add a comment |
Have you verified, that your link.exe is in yourPATH? users.rust-lang.org/t/problems-with-installing-rust-on-windows/…
– hellow
Nov 26 '18 at 10:55
No, I had not, but have just checked and "The term 'link.exe' is not recognized..." if I try to invoke it.
– Jeroen
Nov 26 '18 at 11:10
Have you verified, that your link.exe is in your
PATH? users.rust-lang.org/t/problems-with-installing-rust-on-windows/…– hellow
Nov 26 '18 at 10:55
Have you verified, that your link.exe is in your
PATH? users.rust-lang.org/t/problems-with-installing-rust-on-windows/…– hellow
Nov 26 '18 at 10:55
No, I had not, but have just checked and "The term 'link.exe' is not recognized..." if I try to invoke it.
– Jeroen
Nov 26 '18 at 11:10
No, I had not, but have just checked and "The term 'link.exe' is not recognized..." if I try to invoke it.
– Jeroen
Nov 26 '18 at 11:10
add a comment |
2 Answers
2
active
oldest
votes
Installing any "VC++ toolset" should be enough to get cargo run to link properly. It looks like the minimum dependencies are:
Required dependencies are
VC++ 2017 version 15.7 v14.14 latest v141 toolsandWindows 10 SDK (10.0.17134.0)
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
add a comment |
Note that VC does not add its tools to the path (so that you can have multiple versions of the MS toolchain installed in parallel). Instead it adds entries to your Start menu like: "VC++ 2017 version 15.9 v14.16 command prompt" (not sure of the name), that allow you to start a command prompt with the proper path. This should also be possible from a VS toolbar button or menu entry.
You can't start cargo from a generic command prompt, you need to open the prompt with one of the above solutions.
Alternatively, you need to run c:pathtoyourVSinstallationVCVARS.BAT inside your prompt to set the correct path before running cargo.
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53479270%2fwhich-individual-component-from-the-visual-studio-installer-is-suitable-for-ru%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Installing any "VC++ toolset" should be enough to get cargo run to link properly. It looks like the minimum dependencies are:
Required dependencies are
VC++ 2017 version 15.7 v14.14 latest v141 toolsandWindows 10 SDK (10.0.17134.0)
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
add a comment |
Installing any "VC++ toolset" should be enough to get cargo run to link properly. It looks like the minimum dependencies are:
Required dependencies are
VC++ 2017 version 15.7 v14.14 latest v141 toolsandWindows 10 SDK (10.0.17134.0)
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
add a comment |
Installing any "VC++ toolset" should be enough to get cargo run to link properly. It looks like the minimum dependencies are:
Required dependencies are
VC++ 2017 version 15.7 v14.14 latest v141 toolsandWindows 10 SDK (10.0.17134.0)
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
Installing any "VC++ toolset" should be enough to get cargo run to link properly. It looks like the minimum dependencies are:
Required dependencies are
VC++ 2017 version 15.7 v14.14 latest v141 toolsandWindows 10 SDK (10.0.17134.0)
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
edited Nov 26 '18 at 14:03
Shepmaster
160k16328472
160k16328472
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
answered Nov 26 '18 at 13:34
idursunidursun
5,54512948
5,54512948
add a comment |
add a comment |
Note that VC does not add its tools to the path (so that you can have multiple versions of the MS toolchain installed in parallel). Instead it adds entries to your Start menu like: "VC++ 2017 version 15.9 v14.16 command prompt" (not sure of the name), that allow you to start a command prompt with the proper path. This should also be possible from a VS toolbar button or menu entry.
You can't start cargo from a generic command prompt, you need to open the prompt with one of the above solutions.
Alternatively, you need to run c:pathtoyourVSinstallationVCVARS.BAT inside your prompt to set the correct path before running cargo.
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
add a comment |
Note that VC does not add its tools to the path (so that you can have multiple versions of the MS toolchain installed in parallel). Instead it adds entries to your Start menu like: "VC++ 2017 version 15.9 v14.16 command prompt" (not sure of the name), that allow you to start a command prompt with the proper path. This should also be possible from a VS toolbar button or menu entry.
You can't start cargo from a generic command prompt, you need to open the prompt with one of the above solutions.
Alternatively, you need to run c:pathtoyourVSinstallationVCVARS.BAT inside your prompt to set the correct path before running cargo.
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
add a comment |
Note that VC does not add its tools to the path (so that you can have multiple versions of the MS toolchain installed in parallel). Instead it adds entries to your Start menu like: "VC++ 2017 version 15.9 v14.16 command prompt" (not sure of the name), that allow you to start a command prompt with the proper path. This should also be possible from a VS toolbar button or menu entry.
You can't start cargo from a generic command prompt, you need to open the prompt with one of the above solutions.
Alternatively, you need to run c:pathtoyourVSinstallationVCVARS.BAT inside your prompt to set the correct path before running cargo.
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
Note that VC does not add its tools to the path (so that you can have multiple versions of the MS toolchain installed in parallel). Instead it adds entries to your Start menu like: "VC++ 2017 version 15.9 v14.16 command prompt" (not sure of the name), that allow you to start a command prompt with the proper path. This should also be possible from a VS toolbar button or menu entry.
You can't start cargo from a generic command prompt, you need to open the prompt with one of the above solutions.
Alternatively, you need to run c:pathtoyourVSinstallationVCVARS.BAT inside your prompt to set the correct path before running cargo.
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
edited Nov 26 '18 at 14:56
Shepmaster
160k16328472
160k16328472
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
answered Nov 26 '18 at 14:40
JmbJmb
2,831523
2,831523
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53479270%2fwhich-individual-component-from-the-visual-studio-installer-is-suitable-for-ru%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you verified, that your link.exe is in your
PATH? users.rust-lang.org/t/problems-with-installing-rust-on-windows/…– hellow
Nov 26 '18 at 10:55
No, I had not, but have just checked and "The term 'link.exe' is not recognized..." if I try to invoke it.
– Jeroen
Nov 26 '18 at 11:10