dotfiles: pin the native ninja ahead of the one VS bundles

[dotfiles] / setup-windows.bat

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