Is it possible to cross-build Arm64 executables on GitLab’s shared Windows runners? Trying to run vcpkg install nghttp3:arm64-windows currently fails with
Detecting compiler hash for triplet arm64-windows...
error: in triplet arm64-windows: Unable to find a valid toolchain for requested target architecture arm64.
The selected Visual Studio instance is at: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
The available toolchain combinations are: x86, amd64, x86_amd64, amd64_x86
Reading SaaS runners on Windows (Beta) | GitLab I cannot find architecture specific details but would assume that GCP Windows images are consumed. Server 2019 in Operating system details | Compute Engine Documentation | Google Cloud lists all except T2A machine types.
Not sure what is needed to cross-compile different platform architectures on Windows (i.e. if something similar to qemu on Linux exists).
Googling for the install command led to vcpkg fails to detect installed MSVC arm64 toolchain · Issue #28813 · microsoft/vcpkg · GitHub which provides insights into VS2022 toolchain, and ARM platform support required being enabled. cookbooks/preinstalled-software · main · GitLab.org / Ops Sub-Department / shared-runners / images / gcp / windows-containers · GitLab shows all preinstalled packages. I don’t know how VS 2019 is installed exactly, and what is needed to enable more build support on the CLI. Might be worth investigating the scripts in the repository.
Chocolatey Software | Packages matching workload for Visual Studio 2019 does not provide a workload for ARM.
Suggest adding a comment to the epic in Runner SaaS: Windows Runners on GitLab.com (GA) (&2162) · Epics · GitLab.org · GitLab explaining your usecase and full CI/CD example, to raise awareness. cc @gabrielengel_gl