You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: use setup-msvc-dev action instead of a hard-coded vcvars path
The windows-cmake job set up the MSVC environment by calling a hard-coded
"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary\Build\vcvars64.bat"
in its NMake, clang-cl and Meson steps. The hosted windows-latest image no
longer has Visual Studio installed under that "Enterprise" path, so those steps
started failing with "The system cannot find the path specified."
Set up the developer environment once per job with the
TheMrMilchmann/setup-msvc-dev action -- it locates the installed toolchain (no
hard-coded path or edition) and exports the environment for the following steps
-- and drop all the hard-coded vcvars64.bat calls.
Because that environment now applies to the whole job, force gcc for the MinGW
configure steps; otherwise CMake's "MinGW Makefiles" generator picks up cl.
Assisted-by: claude-code:claude-opus-4-8
0 commit comments