Hello Alexei,
As discussed, I’m submitting a small CI change to add a Windows ARM64 build using MSBuild.
This job extends the existing Windows MSBuild configuration to add an ARM64 build for FreeType on Windows.
Note: This job requires the ARM64 build tools to be installed in the
Visual Studio 2019 environment.
Please let me know if any changes are needed.
Best regards,
Harish
In-Lined patch:
From 5fd96b7e156e224dec69700a23d38278f12619b6 Mon Sep 17 00:00:00 2001
Date: Mon, 12 Jan 2026 11:21:46 +0530
Subject: [PATCH] ci: add Windows ARM64 build using MSBuild
---
.gitlab-ci.yml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 07217fc44..9341efbf0 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -113,6 +113,11 @@ windows msbuild vs2019 amd64:
ARCH: 'amd64'
PLATFORM: 'x64'
+windows msbuild vs2019 arm64:
+ extends: '.build windows msbuild'
+ variables:
+ ARCH: 'arm64'
+ PLATFORM: 'arm64'
# Linux Jobs.
#
--
2.50.1.windows.1
Harish,
This seems straightforward through minor edits of lines 110-114 of .gitlab-ci. yml after duplicating them. MSBuild should support ARM64 already.
Alexei
Hello Everyone,
I am Harish Raja Selvan from
MulticoreWare, India. We are currently working on enabling native builds of various open-source libraries for the Windows on ARM (WoA) platform.
I’d like to start a discussion about extending the FreeType CI pipeline to include Windows on ARM (ARM64) support. I wanted to ask whether setting up a self-hosted Windows on ARM runner would make sense for more comprehensive testing and long-term stability.
Adding Windows on ARM coverage in CI would help ensure consistent build and test validation on this platform. I’d be happy to help contribute configuration changes if this direction seems reasonable.
Thanks for your time.
Regards,
Harish
⚠️ External Email Warning: This message originated from outside the organization (McW).
Be cautious - Never share passwords or click unexpected links/attachments.
<0001-ci-add-Windows-ARM64-build-using-MSBuild.patch>
