Skip to content

Commit 9095217

Browse files
authored
Rollup merge of #60816 - scottmcm:vcpp-download-link, r=alexcrichton
README.md: Mention MSVC 2017+, not 2013(!) LLVM will soon require 2017+ (and our in-tree version just rejected the version of 2015 I was using), so update the mention and provide a link. Ref: https://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library
2 parents 6b29987 + 7171bd1 commit 9095217

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

README.md

+9-3
Original file line numberDiff line numberDiff line change
@@ -128,9 +128,15 @@ build.
128128
#### MSVC
129129
[windows-msvc]: #windows-msvc
130130

131-
MSVC builds of Rust additionally require an installation of Visual Studio 2013
132-
(or later) so `rustc` can use its linker. Make sure to check the “C++ tools”
133-
option.
131+
MSVC builds of Rust additionally require an installation of Visual Studio 2017
132+
(or later) so `rustc` can use its linker. The simplest way is to get the
133+
[Visual Studio Build Tools] and check the “C++ build tools” workload.
134+
135+
[Visual Studio Build Tools]: https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019
136+
137+
At last check (cmake 3.14.3 and msvc 16.0.3) using the 2019 tools fails to
138+
build the in-tree LLVM build with a CMake error, so use 2017 instead by
139+
including the “MSVC v141 – VS 2017 C++ x64/x86 build tools (v14.16)” component.
134140

135141
With these dependencies installed, you can build the compiler in a `cmd.exe`
136142
shell with:

0 commit comments

Comments
 (0)