-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Linking error with MSVC build (2017) #42575
Comments
I didn't say this in my original post, but installing the 2015 tools fixed the issue. Tested both a trivial 'hello world' program and the original problem I was having, which was Racer failing to build at kernel32-sys with a linker error. Neither succeeds with 2017, both succeed with 2015. |
2017 will work from the MSVC build tools shell. Closing as a duplicate of #38584. |
I would argue that the (Rust) documentation still needs to be updated. At least the installation page. As it stands, there is extra work involved in getting Rust on Windows to work with VS Build Tools 2017 or - alternatively - install the 2015 tools instead. This extra work is not mentioned in the Rust install docs for Windows. If nothing is done, I suspect you will have future Rust newcomers complaining about the same thing, which is contrary to the current goal of making Rust easier for newcomers to learn. Just my two cents. |
The above content is from the official document. |
I found issue #29479 after searching for the linking error I was getting, and I believe that this is a new issue. Same error, but I had VS Build Tools 2017 installed. When I installed Rust, I followed the link from the installation page to the 2015 build tools, which currently offers a link to the 2017 tools. I double-checked the Rust installation page and since it said "...requires the C++ build tools for Visual Studio 2013 or later", I went ahead and installed 2017.
In any event, I think, at the very least, the docs should be updated to reflect that 2017 will not work, for the time being.
The text was updated successfully, but these errors were encountered: