On 27 Jan 2026, at 07:29, Harish Raja Selvan 
<[email protected]> wrote:
> 
> Thanks for the explanation.
> I wanted to share that I’ve successfully built libtiff natively on Windows on 
> ARM64 (X Elite laptop) using the MSVC compiler, without requiring any code 
> changes. 
> Since Windows on ARM Docker images are not currently supported, I wanted to 
> ask whether it would be possible to set up a self-hosted ARM64 runner, if we 
> are able to provide suitable WoA hardware.
> Please let me know your thoughts.

Note that Windows on ARM docker images *are* supported and exist.

See https://mcr.microsoft.com/v2/windows/servercore/tags/list and note at the 
bottom:

    "ltsc2025-amd64",
    "ltsc2025-arm64”,

Our CI is now using the ltsc2025-amd64 image.  But there is an ARM64 version 
too.

The provision of suitable hardware is a kind offer, but the main problem is the 
ongoing support and administration of the systems to keep them running and 
up-to-date.  That’s the primary reason I switched the Windows AMD64 builds over 
to use containers ( https://gitlab.com/codelibre/containers?filter=libtiff ), 
since it’s then possible to maintain all of the build environment definitions 
and update them under our control, as well as having a clean and unique 
environment for each build.  If an equivalent set of containers can be built 
for ARM64 then it becomes a bit more viable, but it’s still a big time 
commitment to set all that up.  Troubleshooting and support of the old Windows 
build systems and the bring-up and testing and container building of the new 
Windows build systems has already taken several working days out of this month 
for me, and I don’t want to increase this further, especially when it’s not 
really increasing the effective test coverage that much.  I’d like to see how 
the existing setup copes for a few months before adding more systems.  It may 
be viable later on, but for now the existing ones are more than enough of a 
task to manage.

Kind regards,
Roger

_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff

Reply via email to