X-Git-Url: https://vilimpoc.org/repos/dotfiles/blobdiff_plain/cd774a195092cd0ab4c8e92862d0c5cf7e04f195..d254a9bebd5448269d34a5c6dfcd36b646659b31:/setup-windows.bat diff --git a/setup-windows.bat b/setup-windows.bat index bd248a9..c9c7efb 100644 --- a/setup-windows.bat +++ b/setup-windows.bat @@ -10,18 +10,34 @@ @rem --------------------------------------------------------------------------- @rem Host architecture @rem -@rem PROCESSOR_ARCHITECTURE alone is not enough: a 32-bit cmd.exe under emulation -@rem reports x86 and stashes the real one in PROCESSOR_ARCHITEW6432. Check both, -@rem so this is right however the script was launched. +@rem The environment variables are not enough, and the failure is silent. A 32-bit +@rem cmd.exe under emulation reports x86 and stashes the real one in +@rem PROCESSOR_ARCHITEW6432 - that pair is handled below - but an EMULATED x64 +@rem cmd.exe on an ARM64 box reports AMD64 with PROCESSOR_ARCHITEW6432 unset, and +@rem nothing in the environment contradicts it. Launching this script from an x64 +@rem shell (Git Bash, for one) is enough to hit that, and measured here it gives: +@rem PROCESSOR_ARCHITECTURE AMD64 +@rem HKLM\...\Session Manager\Environment ARM64 <- the real one @rem -@rem The value drives two things below, and nothing else - winget resolves the +@rem So take the machine-level registry value as the answer and keep the +@rem environment pair only as the fallback. The registry key is per-machine and +@rem not subject to per-process emulation, and it is not one of the redirected +@rem hives. This is load-bearing now: %IS_ARM64% decides which packages are +@rem installed at all, so reading it wrong provisions the wrong machine. +@rem +@rem The value drives three things below, and nothing else - winget resolves the @rem installer architecture on its own (native first, then whatever the box can @rem emulate), so the ordinary installs need no help: @rem - VirtualBox is skipped on ARM64 (see below) +@rem - the x64-only package set is skipped on ARM64 (see :x64only) @rem - the summary tells you which tools you got as emulated x64 @rem --------------------------------------------------------------------------- set "HOST_ARCH=%PROCESSOR_ARCHITECTURE%" if defined PROCESSOR_ARCHITEW6432 set "HOST_ARCH=%PROCESSOR_ARCHITEW6432%" +@rem reg.exe by full path, and NOT through a pipe to find/findstr: both of those +@rem are shadowable by anything earlier on the PATH, and a POSIX `find` on the +@rem PATH turns this into a silent no-op that leaves the emulated answer standing. +for /f "tokens=1,2,*" %%A in ('%SystemRoot%\System32\reg.exe query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /v PROCESSOR_ARCHITECTURE 2^>nul') do if /i "%%A"=="PROCESSOR_ARCHITECTURE" set "HOST_ARCH=%%C" set "IS_ARM64=0" if /i "%HOST_ARCH%"=="ARM64" set "IS_ARM64=1" echo [setup-windows] Host architecture: %HOST_ARCH% @@ -51,6 +67,30 @@ if "%ELEV%"=="NOLUA" ( echo [setup-windows] at each one, and a summary before the elevated half. ) +@rem --------------------------------------------------------------------------- +@rem ARM64 is a lean build box, x64 is the full workstation +@rem +@rem The ARM64 machine here is a small VM, and everything it was installing +@rem without a native build was going to run under Prism emulation anyway. So the +@rem two architectures now provision different things on purpose: x64 keeps the +@rem full set, ARM64 installs ONE compiler - MSVC from Visual Studio - and +@rem nothing that merely duplicates it or that exists only as an x64 binary. +@rem +@rem Dropped on ARM64, and where each one is dropped: +@rem Brave.Brave here no ARM64 build; Edge is in-box and native +@rem WinMerge.WinMerge here ARM64 build is machine-scope only +@rem LLVM.LLVM here second Clang, dropped with VS's clang-cl +@rem NASM.NASM here x86/x64 assembler; ARM64 uses MSVC's armasm64 +@rem Google.AndroidGPUInspector here x64-only, profiles Android devices +@rem OpenCppCoverage.OpenCppCoverage here x86/x64 only; cannot instrument ARM64 binaries +@rem VS Clang/LLVM component with-uac see $ClangComponents +@rem Windows Driver Kit with-uac see the WDK step +@rem BinSkim no-uac NuGet publishes win-x64 only +@rem +@rem :x64only at the bottom of this file is the one place that decision is +@rem applied, so the skip and its reason land in the log together. +@rem --------------------------------------------------------------------------- + @rem --- Non-admin (per-user) winget installs --- @rem @rem No --architecture anywhere on purpose. winget already picks the best @@ -67,7 +107,7 @@ if "%ELEV%"=="NOLUA" ( @rem (ARM64). On ARM64, run the *64a.exe variants - plain procexp.exe is the x86 @rem one and will run emulated. winget install Anthropic.ClaudeCode -winget install Brave.Brave +call :x64only Brave.Brave "no ARM64 build - the emulated x64 browser is the slowest thing on the box, and Edge is in-box and native" winget install Git.Git winget install Microsoft.PowerShell Microsoft.Sysinternals.ProcessExplorer Microsoft.Sysinternals.ProcessMonitor Microsoft.Sysinternals.SDelete Microsoft.VisualStudioCode Microsoft.WindowsTerminal winget install Python.Python.3.13 @@ -79,17 +119,11 @@ winget install Python.Python.3.13 @rem unelevated, winget's scope preference beats its architecture preference and @rem you silently get the emulated x64 build. @rem -@rem So ask for arm64 explicitly, and fall back to the default when that cannot be -@rem installed - which is exactly the standard-user case, where the machine-scope -@rem installer has nowhere to go. The fallback is the x64 build under emulation: -@rem a diff tool is not a hot path, and a working WinMerge beats none. The -@rem architecture audit at the end of setup-windows-no-uac.ps1 reports which one -@rem you ended up with. -if "%IS_ARM64%"=="1" ( - winget install WinMerge.WinMerge --architecture arm64 || winget install WinMerge.WinMerge -) else ( - winget install WinMerge.WinMerge -) +@rem That asymmetry is why ARM64 no longer installs it at all: the only build a +@rem normal user can install there is the emulated one, and asking for --architecture +@rem arm64 just fails unless the run is elevated. VS Code's diff view and +@rem `git difftool` cover the same ground natively. +call :x64only WinMerge.WinMerge "upstream ships ARM64 as a machine-scope installer only, so an unelevated winget can install nothing but the emulated x64 build" @rem --- Build drivers, standalone and native --- @rem @@ -117,24 +151,27 @@ if "%IS_ARM64%"=="1" ( @rem whole machine. winget install Ninja-build.Ninja -@rem --- Second, independent Clang: compiler diversity --- +@rem --- Second, independent Clang: compiler diversity, on x64 only --- @rem -@rem The elevated half installs Visual Studio's Clang component (clang-cl, native -@rem ARM64). This is a DIFFERENT LLVM: the upstream release, on its own schedule -@rem and usually several major versions ahead of the one VS bundles, installed to +@rem On x64 the elevated half installs Visual Studio's Clang component (clang-cl). +@rem This is a DIFFERENT LLVM: the upstream release, on its own schedule and +@rem usually several major versions ahead of the one VS bundles, installed to @rem C:\Program Files\LLVM rather than inside the VS tree. Two Clang majors plus @rem MSVC over the same sources is the point - it is what catches the bugs a @rem single toolchain agrees with itself about. @rem -@rem Native on ARM64: the manifest resolves to LLVM--woa64.exe ("Windows on -@rem Arm 64"), not the x64 build. +@rem NOT ON ARM64, and not for lack of a native build - the manifest does resolve +@rem to LLVM--woa64.exe there. It is dropped because the ARM64 box carries +@rem MSVC alone: with VS's clang-cl component gone too, a third compiler with +@rem nothing to disagree with is just disk. Do the multi-compiler build on the +@rem x64 machine, which keeps all three. @rem -@rem PATH ORDER MATTERS if you use it. Should this installer put its bin on the -@rem PATH, a bare `clang-cl` resolves to the upstream one while CMake's +@rem PATH ORDER MATTERS on x64 if you use it. Should this installer put its bin on +@rem the PATH, a bare `clang-cl` resolves to the upstream one while CMake's @rem `-T ClangCL` toolset keeps using the VS copy - so the two can be selected @rem independently, but only if you know which one you are asking for. Prefer @rem -DCMAKE_CXX_COMPILER with a full path when you care. -winget install LLVM.LLVM +call :x64only LLVM.LLVM "ARM64 carries MSVC alone - VS's clang-cl is dropped there too, so a second Clang has nothing to cross-check against" @rem x64-only manifest: winget falls back to the x64 installer on ARM64 and it runs @rem under Prism emulation. Harmless for what it does here - iperf3 is a network @@ -142,11 +179,15 @@ winget install LLVM.LLVM winget install ar51an.iPerf3 @rem NASM assembles x86/x86-64 only - there is no ARM64 target in it and no ARM64 -@rem build of it. Installed on ARM64 anyway (as emulated x64) because this box -@rem still cross-compiles x86/x64 binaries, where NASM is the assembler that -@rem builds them. If you only ever target ARM64, nothing here uses it: the ARM64 -@rem assembler is armasm64.exe, which ships with MSVC. -winget install NASM.NASM +@rem build of it. x64 keeps it; ARM64 does not, because an emulated assembler is +@rem only worth carrying if you cross-compile x86/x64 here, and that work belongs +@rem on the x64 box. The ARM64 assembler is armasm64.exe, which ships with MSVC. +@rem +@rem Its installer is also one of the two here that fall back to a per-user +@rem directory when it cannot write to Program Files - C:\Users\\AppData\ +@rem Local\bin\NASM, registered nowhere, so `winget uninstall` cannot find it +@rem afterwards. Uninstall.exe in that directory is the only way back out. +call :x64only NASM.NASM "x86/x86-64 assembler with no ARM64 target and no ARM64 build - MSVC's armasm64.exe is the native one" @rem VirtualBox has no ARM64 Windows host build, and the x64 one cannot be made to @rem work by emulation: a hypervisor is kernel-mode, and its x64 driver will not @@ -181,11 +222,15 @@ if "%IS_ARM64%"=="1" ( @rem NOTE none of these is a build-blocker: the .NET SDK is only here for the WiX @rem MSI tooling, CMake also ships inside Visual Studio, AGI profiles Android @rem devices, and OpenCppCoverage cannot instrument ARM64 binaries anyway. +@rem +@rem On ARM64 the group is just the first two - AGI and OpenCppCoverage are in the +@rem x64-only set, so there they are skipped before elevation is even consulted. @rem --------------------------------------------------------------------------- if "%ELEV%"=="NOLUA" ( echo. echo [setup-windows] Skipping the machine-wide installers - this account cannot elevate: - echo [setup-windows] Microsoft.DotNet.SDK.10, Kitware.CMake, Google.AndroidGPUInspector, OpenCppCoverage. + echo [setup-windows] Microsoft.DotNet.SDK.10 and Kitware.CMake, plus - on x64 only - + echo [setup-windows] Google.AndroidGPUInspector and OpenCppCoverage. echo [setup-windows] None blocks a build. Re-run from an administrator account to get them. echo. goto :after_admin_pkgs @@ -193,7 +238,7 @@ if "%ELEV%"=="NOLUA" ( winget install Microsoft.DotNet.SDK.10 winget install Kitware.CMake -winget install Google.AndroidGPUInspector +call :x64only Google.AndroidGPUInspector "x64-only build, and it profiles Android devices rather than anything compiled here" @rem OpenCppCoverage: native (PE) line coverage for the C++ binaries. run-coverage-occ.py drives the @rem pytest suite under it to produce an HTML report (the binaries under test build with PDBs, @@ -201,13 +246,12 @@ winget install Google.AndroidGPUInspector @rem @rem x86/x64 only, and unlike the other emulated tools that is a real limit rather @rem than a slowdown: it collects coverage by debugging the process under test and -@rem stepping x86/x64 instructions, so it can cover the x86/x64 binaries this box -@rem cross-compiles but NOT an ARM64 one. For ARM64 coverage, build the ARM64 -@rem binaries with /fsanitize-coverage or use the x64 build for the coverage run. -winget install OpenCppCoverage.OpenCppCoverage +@rem stepping x86/x64 instructions, so it can cover x86/x64 binaries but NOT an +@rem ARM64 one. That is what puts it in the x64-only set: on ARM64 it could only +@rem ever cover the cross-compiled x64 build, which is a job for the x64 box. +call :x64only OpenCppCoverage.OpenCppCoverage "it collects coverage by stepping x86/x64 instructions, so it cannot instrument an ARM64 binary at all" :after_admin_pkgs -if "%IS_ARM64%"=="1" echo [setup-windows] NOTE: OpenCppCoverage is x86/x64-only - it cannot instrument ARM64 binaries. Run coverage against the x64 build. @rem --- WiX 5.0.2, pinned on purpose --- @rem WiX packages our proprietary software into MSIs, and the version is pinned to keep that @@ -298,8 +342,8 @@ echo [setup-windows] so Windows offers no way to elevate - there is no prompt echo [setup-windows] 'Start-Process -Verb RunAs' is silently ignored and reports success, which is why echo [setup-windows] this used to look like a cancelled prompt. echo [setup-windows] -echo [setup-windows] Not installed: Visual Studio components ^(including clang-cl^), the WDK, -echo [setup-windows] rsync, and the OpenSSH server. Everything per-user above is unaffected. +echo [setup-windows] Not installed: Visual Studio and its MSVC toolchain, rsync, and the OpenSSH +echo [setup-windows] server. Everything per-user above is unaffected. echo [setup-windows] echo [setup-windows] To finish the box, either sign in to an administrator account and re-run this echo [setup-windows] script, or have an administrator run setup-windows-with-uac.ps1 there. Then @@ -374,21 +418,57 @@ if "%UAC_RC%"=="SKIPPED" echo [setup-windows] Per-user setup complete; the eleva @rem py -m pip install "headroom-ai[all]" @rem npm install headroom-ai -@rem Pillow publishes win_arm64 wheels alongside win_amd64, so `py` - the ARM64 -@rem Python winget just installed - gets a native wheel and never falls back to -@rem building from source. Any package WITHOUT an ARM64 wheel does fall back, and -@rem that source build needs the MSVC toolchain the elevated half installs. -py -m pip install Pillow +@rem --- Find an interpreter by path, rather than trusting `py` --- +@rem +@rem `py -m pip install Pillow` used to be this line, and it failed with +@rem 'py' is not recognized as an internal or external command +@rem for two independent reasons, which look identical at the prompt: +@rem +@rem 1. PATH staleness. winget installed Python a few lines above, but this cmd +@rem session inherited its environment before that, so nothing winget added +@rem is visible here. Same problem the DOTNET_EXE lookup solves above, and it +@rem would bite even where the launcher IS installed. +@rem +@rem 2. The launcher may simply not be there. Measured on the ARM64 box: every +@rem other Python component registered - Core Interpreter, Executables, +@rem Standard Library, pip Bootstrap, Tcl/Tk, Add to Path - and there is no +@rem launcher entry and no py.exe anywhere on disk, while the Launcher +@rem directory it would occupy is on the user PATH but does not exist. +@rem +@rem So resolve an interpreter by full path and prefer the launcher only when it +@rem is real. python.exe is the thing that actually has to exist; `py` is a +@rem convenience shim that picks between several of them, and there is exactly one +@rem here. Reverse name order so the newest Python wins, and require python.exe +@rem inside the directory - a half-removed version leaves the folder behind with +@rem only Doc and Lib in it, which is exactly what this box has. +set "PY_EXE=" +if exist "%LOCALAPPDATA%\Programs\Python\Launcher\py.exe" set "PY_EXE=%LOCALAPPDATA%\Programs\Python\Launcher\py.exe" +if not defined PY_EXE if exist "%WINDIR%\py.exe" set "PY_EXE=%WINDIR%\py.exe" +if not defined PY_EXE for /f "delims=" %%P in ('dir /b /ad /o-n "%LOCALAPPDATA%\Programs\Python\Python3*" 2^>nul') do if not defined PY_EXE if exist "%LOCALAPPDATA%\Programs\Python\%%P\python.exe" set "PY_EXE=%LOCALAPPDATA%\Programs\Python\%%P\python.exe" + +@rem Pillow publishes win_arm64 wheels alongside win_amd64, so the ARM64 Python +@rem winget just installed gets a native wheel and never falls back to building +@rem from source. Any package WITHOUT an ARM64 wheel does fall back, and that +@rem source build needs the MSVC toolchain the elevated half installs. +if not defined PY_EXE ( + echo [setup-windows] WARNING: no Python interpreter found; skipping the Pillow install. + echo [setup-windows] Looked for the py launcher, then %LOCALAPPDATA%\Programs\Python\Python3*\python.exe. +) else ( + echo [setup-windows] Python: %PY_EXE% + "%PY_EXE%" -m pip install Pillow +) if "%IS_ARM64%"=="1" ( echo. echo [setup-windows] ARM64 notes: echo [setup-windows] native ARM64: Git, Python, .NET SDK, PowerShell, VS Code, Windows Terminal, - echo [setup-windows] WinMerge, Brave, Sysinternals ^(the *64a.exe variants^), - echo [setup-windows] Claude Code, CMake, Ninja, and the SDK/WPT tools. - echo [setup-windows] compilers : MSVC and clang-cl from Visual Studio 2026, plus upstream - echo [setup-windows] LLVM - all three native ARM64, two different Clang majors. - echo [setup-windows] emulated x64: iperf3, NASM, OpenCppCoverage, BinSkim, rsync.exe, AGI. + echo [setup-windows] Sysinternals ^(the *64a.exe variants^), Claude Code, CMake, + echo [setup-windows] Ninja, and the SDK/WPT tools. + echo [setup-windows] compiler : MSVC from Visual Studio 2026, native ARM64. One compiler by + echo [setup-windows] design - clang-cl and upstream LLVM are x64-box only. + echo [setup-windows] emulated x64: iperf3, which is network-bound anyway. + echo [setup-windows] not here : Brave, WinMerge, LLVM, NASM, AGI, OpenCppCoverage, BinSkim + echo [setup-windows] and the WDK - dropped on ARM64, see the x64-only set above. echo [setup-windows] unavailable : VirtualBox, the Windows 7 x86 test VM, Intel VTune, echo [setup-windows] and the v141 / Windows XP targeting toolset. ) @@ -396,6 +476,27 @@ if "%IS_ARM64%"=="1" ( @rem landed on this run - so point at the audit, which reports the actual state. if "%ELEV%"=="NOLUA" ( echo [setup-windows] NOT on this box: everything needing elevation was skipped, including - echo [setup-windows] Visual Studio's clang-cl, the .NET SDK and CMake. The + echo [setup-windows] Visual Studio's MSVC, the .NET SDK and CMake. The echo [setup-windows] architecture audit above lists what is really installed. ) + +exit /b 0 + +@rem --------------------------------------------------------------------------- +@rem :x64only "" +@rem +@rem Install a package on x64 and skip it on ARM64, saying why. One subroutine +@rem rather than a gate at each call site so that the reason is never separated +@rem from the skip: the log line a future reader sees is the same text this file +@rem carries, and there is exactly one place to change the policy. +@rem +@rem The reason is a real argument, not a comment, because the interesting case is +@rem reading the run log six months later and wondering where NASM went. +@rem --------------------------------------------------------------------------- +:x64only +if not "%IS_ARM64%"=="1" ( + winget install %1 + goto :eof +) +echo [setup-windows] Skipping %1 on ARM64: %~2 +goto :eof