windows: build with Visual Studio 2026 / newer MSVC toolsets

[exzile]

Fixes #4333.

The Windows build scripts hardcode Visual Studio 2022 Build Tools and a specific MSVC toolset version, so a machine with only Visual Studio 2026 (v18) cannot build OVMS. This PR detects the installed Visual Studio and toolset, and fixes a couple of newer-toolchain breakages it surfaced.

Changes

1. Auto-detect Visual Studio via vswhere (windows_install_build_dependencies.bat, windows_build.bat, windows_setupvars.bat, windows_test.bat)

• Replaces the hardcoded C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools with vswhere -latest -requires ...VC.Tools.x86.x64 -property installationPath (works with BuildTools/Community/Pro/Enterprise).
• Derives the CMake generator (Visual Studio <major> <year>) from the detected major version instead of the literal "Visual Studio 17 2022".
• Auto-detects the installed MSVC toolset version instead of the pinned 14.44.35207.

2. Allow newer MSVC toolsets to compile XLA (.bazelrc)

• MSVC 14.51+ (VS 2026) raises C5285 ("specializing std::is_signed is forbidden") on TensorFlow/XLA's quantized-type specializations (xla/tsl/framework/type_traits.h). XLA builds with /WX, so it becomes a fatal C2220. Added build:windows --copt=/wd5285 (+ --host_copt) to suppress this benign upstream warning. Without it, only the older 14.44 toolset builds.

3. OpenCV generator default toolset / CMake 4.x (windows_install_build_dependencies.bat)

• Dropped the hardcoded -T v142 (VS 2019 toolset, absent on a VS 2026 box); cmake uses the generator's default (installed) toolset.
• Pass -D PYTHON3_EXECUTABLE and disable the OpenCV python bindings — newer CMake (4.x) errors in OpenCV's python auto-detection (find_package called with invalid argument "OFF"); OVMS only needs the C++ libs.

4. Non-privileged GenAI link (windows_install_build_dependencies.bat)

• mklink /d → mklink /j for the openvino link. A directory junction is functionally equivalent here and does not require SeCreateSymbolicLinkPrivilege (admin / Developer Mode), so the dependency install works in a non-elevated shell.

Testing

• Built ovms.exe end-to-end on Visual Studio 2026 (18.7, MSVC 14.51) with windows_install_build_dependencies.bat + windows_build.bat opt --with_python — produces a working server (OpenVINO Model Server 2026.3.0).
• Not re-tested on VS 2022 (no VS2022 box available); the vswhere/generator/toolset detection resolves the 2022 values by the same logic, and the /wd5285 + OpenCV changes are no-ops on the older toolset.

Notes

• CMake must be on PATH (the VS "C++ CMake tools" component or a standalone install).

[Copilot]

Pull request overview

Updates OVMS Windows build tooling to work on newer Visual Studio/MSVC installations by detecting the installed VS instance/toolset at runtime and addressing newer-toolchain build breakages (notably XLA warnings treated as errors).

Changes:

• Auto-detect Visual Studio installation path via vswhere in Windows .bat scripts instead of hardcoding VS 2022 Build Tools paths.
• Auto-detect the installed MSVC toolset version in build/setup/test scripts instead of pinning a specific version.
• Allow MSVC 14.51+ to compile XLA by suppressing warning C5285 in Windows Bazel config.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
windows_install_build_dependencies.bat	Detects VS + generator via vswhere, switches GenAI link to junction, adjusts CMake/OpenCV configuration for newer toolchains.
windows_build.bat	Detects VS via vswhere and auto-detects MSVC toolset version for Bazel builds.
windows_setupvars.bat	Detects VS via vswhere and auto-detects MSVC toolset version for environment setup.
windows_test.bat	Detects VS via vswhere and auto-detects MSVC toolset version for Bazel test builds.
.bazelrc	Suppresses MSVC warning C5285 on Windows to prevent /WX failures in XLA builds on newer toolsets.