-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Does not work with latest Windows 10 SDK #5
Comments
I look for |
After trying to read the shitty |
I checked and |
I've found the problem - But on the newest Windows SDK, the executable has been moved to It looks like the |
I'd be grateful if you tested the referenced commit; I tried to do my best but there's only so far I can go without an actual test env for this. |
It worked! Thanks. Now all that's left is for |
Does it really work? I'm really surprised. I'll release with patch bump so all crates that depend on this one get the update automatically. Thanks for the help! |
Released in |
Hello, I tried to install the cargo-update crate and ran into an issue. I believe it is caused by this crate, and the way it handles finding RC.exe.
The reason I don't have RC.exe in my
$PATH
is because since VS 2017, you can have multiple installed versions of VS 2017 on the same machine, and they are not added to the path anymore.Now, I do have VS 2017 installed, and the C++ build tools, and Rust nightly does work and uses the VS 2017 linker. Is there a way for this crate to support VS 2017 too?
The solution for Rust was to just update the gcc crate, which supports VS 2017 out of the box.
A temporary solution I found is: open the "x64 Native Tools Command Prompt for VS 2017", and run
cargo install
from there. But, again, it would be great if this crate worked with VS 2017 without special preparation.Some more information:
Finding installed Visual C++ tools for Visual Studio 2017
The text was updated successfully, but these errors were encountered: