Skip to content

[docs] Remove Visual Studio 2017 references and bump VS 2019 to VS 2022 #70759

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 10, 2025
Merged

[docs] Remove Visual Studio 2017 references and bump VS 2019 to VS 2022 #70759

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions clang/www/get_started.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ <h3 id="buildWindows">Using Visual Studio</h3>
project files. Get it from:
<a href="https://cmake.org/download/">
https://cmake.org/download/</a></li>
<li><b>Visual Studio 2019 16.7 or later</b></li>
<li><b>Visual Studio 2019 16.7 or later</b>. This tutorial assumes Visual Studio 2022.</li>
<li><b>Python</b>. It is used to run the clang test suite. Get it from:
<a href="https://www.python.org/download/">
https://www.python.org/download/</a></li>
Expand Down Expand Up @@ -156,8 +156,8 @@ <h3 id="buildWindows">Using Visual Studio</h3>
<li><tt>mkdir build</tt> (for building without polluting the source dir)</li>
<li><tt>cd build</tt></li>
<li>
If you are using Visual Studio 2019:
<tt>cmake -DLLVM_ENABLE_PROJECTS=clang -G "Visual Studio 16 2019" -A x64 -Thost=x64 ..\llvm</tt><br/>
If you are using Visual Studio 2022:
<tt>cmake -DLLVM_ENABLE_PROJECTS=clang -G "Visual Studio 17 2022" -A x64 -Thost=x64 ..\llvm</tt><br/>
<tt>-Thost=x64</tt> is required, since the 32-bit linker will run out of memory.
</li>
<li>To generate x86 binaries instead of x64, pass <tt>-A Win32</tt>.</li>
Expand Down Expand Up @@ -195,12 +195,12 @@ <h3 id="buildWindowsNinja">Using Ninja alongside Visual Studio</h3>
<li>If you open the start menu and search for "Command Prompt", you should
see shortcuts created by Visual Studio to do this. To use native x64
tools, choose the one titled "x64 Native Tools Command Prompt for VS
2017".</li>
2022".</li>
<li> Alternatively, launch a regular <tt>cmd</tt> prompt and run the
appropriate vcvarsall.bat incantation. To get the 2017 x64 tools, this
appropriate vcvarsall.bat incantation. To get the 2022 x64 tools, this
would be:<br/>
<tt>"C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" x64</tt>
<tt>"C:\Program Files\Microsoft Visual
Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64</tt>
</li>
</ul>
</li>
Expand Down