X-Git-Url: https://vilimpoc.org/repos/dotfiles/blobdiff_plain/649b04df2966260f38a18d5225a68bd4e0896b95..3e0aa9fcdd4d04bd4d0714668af9af5fd200cb42:/setup-windows.bat?ds=sidebyside

diff --git a/setup-windows.bat b/setup-windows.bat
index c91262c..05e65eb 100644
--- a/setup-windows.bat
+++ b/setup-windows.bat
@@ -62,9 +62,13 @@ winget install WinMerge.WinMerge
 @rem     graph, which makes it the one tool here where emulation is actually paid
 @rem     over and over, and ninja-winarm64.zip is a native build. Worth having.
 @rem
-@rem Both are on the machine/user PATH after install, so a bare `cmake -G Ninja`
-@rem picks these up. Inside a VS Developer prompt the VS copies may come first;
-@rem that is fine for cmake (same architecture) and is the case to watch for ninja.
+@rem Which ninja wins inside a VS Developer Command Prompt: the native one. VS
+@rem adds its copy from Common7\Tools\vsdevcmd\ext\cmake.bat with
+@rem     set "PATH=%PATH%;...\CMake\bin;...\CMake\Ninja"
+@rem which APPENDS, so the VS directories sit at the very end of the composed
+@rem PATH, behind every machine and user entry. setup-windows-no-uac.ps1 then
+@rem pins the native ninja's directory to the FRONT of the user PATH so the
+@rem margin does not depend on two append orders staying as they are.
 winget install Kitware.CMake
 winget install Ninja-build.Ninja