mirror of
https://github.com/ilammy/msvc-dev-cmd.git
synced 2026-09-06 21:57:19 +08:00
Alexei Lozovsky
840499b504
Recently added Visual Studio location with "vswhere" seems to be very slow when using "-find" with path patterns. As in, 5 minutes slow. vswhere does not provide much insight into why this happens, but I guess that's because filesystem operations (and search in particular) are not very fast on Windows. Improve the search performance by combining vswhere with probing. Use vswhere to locate the installation root, and then probe around for the batch script we need. Also, don't use vswhere for Visual Studio 2015 as it does not seem to work. Rely only on probing here. And also, add some debug logs so that it's possible to track which path has been used, if you're interested in it.
msvc-dev-cmd
GitHub Action for configuring Developer Command Prompt for Microsoft Visual C++.
This sets up the environment for compiling C/C++ code from command line.
Supports Windows. Does nothing on Linux and macOS.
Inputs
arch– target architecture- native compilation:
x86,x64(default),amd64(synonym for x64) - cross-compilation:
x86_amd64,x86_arm,x86_arm64,amd64_x86,amd64_arm,amd64_arm64
- native compilation:
sdk– Windows SDK to use- do not specify to use the default SDK
- or specify full Windows 10 SDK number (e.g,
10.0.10240.0) - or write
8.1to use Windows 8.1 SDK
toolset– select VC++ compiler toolset version- do not specify to use the default toolset
14.0for VC++ 2015 Compiler Toolset14.XXfor the latest 14.XX toolset installed (e.g,14.11)14.XX.YYYYYfor a specific full version number (e.g,14.11.25503)
uwp– settrueto build for Universal Windows Platform (i.e., for Windows Store)spectre– settrueto use Visual Studio libraries with Spectre mitigations
Example usage
jobs:
test:
- uses: actions/checkout@v1
- uses: ilammy/msvc-dev-cmd@v1
- name: Build something requiring CL.EXE
run: |
cmake -G "NMake Makefiles" .
nmake
# ...
License
MIT, see LICENSE.