adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

patch 9.0.0528: MS-Windows: no batch files for more recent MSVC versions

Browse Source 
Problem:    MS-Windows: no batch files for more recent MSVC versions.
Solution:   Add batch files for 2017, 2019 and 2022. (Ken Takata,
            closes #11184)
This commit is contained in:
K.Takata
2022-09-21 11:56:41 +01:00
committed by Bram Moolenaar
parent 2b1ddf19f8
commit c3430cb583
7 changed files with 123 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/INSTALLpc.txt
View File

@ -70,10 +70,15 @@ Visual Studio
Building with Visual Studio (VS2015, VS2017, VS2019 and VS2022) is
straightforward. Older versions probably don't work.
Visual Studio installed a batch file called vcvars32.bat, which you must
Visual Studio installed a batch file called vcvarsall.bat, which you must
run to set up paths for nmake and MSVC. We provide a batch file
"msvc2015.bat" for this. You may need to edit it if you didn't instal Visual
Studio in the standard location.
If you use VS2017 or later, you can use "msvc-latest.bat" (or "msvc2017.bat"
and so on for the specific version). You must specify the architecture (e.g.
"x86", "x64", etc.) as the first argument when you use this. If you use VS2017
Express, you must use "x86_amd64" instead of "x64" for targeting the x64
platform.
To build Vim from the command line with MSVC, use Make_mvc.mak.