diff options
author | K.Takata <kentkt@csc.jp> | 2022-09-21 11:56:41 +0100 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2022-09-21 11:56:41 +0100 |
commit | c3430cb583ff05722e33195e4818c88a59bb2fee (patch) | |
tree | 4d4ab9029148e52bba7bb502f875918fbbc66956 /src/INSTALLpc.txt | |
parent | 2b1ddf19f8f14365d0b998b4ac12ca85c0923475 (diff) | |
download | vim-git-c3430cb583ff05722e33195e4818c88a59bb2fee.tar.gz |
patch 9.0.0528: MS-Windows: no batch files for more recent MSVC versionsv9.0.0528
Problem: MS-Windows: no batch files for more recent MSVC versions.
Solution: Add batch files for 2017, 2019 and 2022. (Ken Takata,
closes #11184)
Diffstat (limited to 'src/INSTALLpc.txt')
-rw-r--r-- | src/INSTALLpc.txt | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/src/INSTALLpc.txt b/src/INSTALLpc.txt index a73f71894..9a286447c 100644 --- a/src/INSTALLpc.txt +++ b/src/INSTALLpc.txt @@ -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. |