Request to add Windows on ARM CI support for FreeType
Harish Raja Selvan <[email protected]> Mon, 5 Jan 2026 06:51:44 +0000
| Newsgroups | gmane.comp.fonts.freetype.devel |
|---|---|
| Message-ID | <MA5P287MB4625E7CBB2BFBA3AE5C9A0EA9EBBA@MA5P287MB4625.INDP287.PROD.OUTLOOK.COM> |
--_000_MA5P287MB4625E7CBB2BFBA3AE5C9A0EA9EBBAMA5P287MB4625INDP_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hello Everyone,
I am Harish Raja Selvan from MulticoreWare, India<https://multicorewareinc.=
com/>. We are currently working on enabling native builds of various open-s=
ource libraries for the Windows on ARM (WoA) platform.
I=92d like to start a discussion about extending the FreeType CI pipeline t=
o include Windows on ARM (ARM64) support. I wanted to ask whether setting u=
p a self-hosted Windows on ARM runner would make sense for more comprehensi=
ve testing and long-term stability.
Adding Windows on ARM coverage in CI would help ensure consistent build and=
test validation on this platform. I=92d be happy to help contribute config=
uration changes if this direction seems reasonable.
Thanks for your time.
Regards,
Harish
--_000_MA5P287MB4625E7CBB2BFBA3AE5C9A0EA9EBBAMA5P287MB4625INDP_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Calibri, He=
lvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class=3D"elemen=
tToProof">
Hello Everyone,</div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Calibri, He=
lvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class=3D"elemen=
tToProof">
I am Harish Raja Selvan from <a rel=3D"noreferrer noopener" title=3D"https:=
//multicorewareinc.com/" class=3D"fui-Link ___1q1shib f2hkw1w f3rmtva f1ewt=
qcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnb=
mjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1=
f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsl=
e3fq f17ae5zn OWAAutoLink" id=3D"OWA4988b5b0-bec8-21ad-6f72-f751eaf2efd9" t=
arget=3D"_blank" href=3D"https://multicorewareinc.com/">
MulticoreWare, India</a>. We are currently working on enabling native build=
s of various open-source libraries for the Windows on ARM (WoA) platform.</=
div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Calibri, He=
lvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class=3D"elemen=
tToProof">
I=92d like to start a discussion about extending the FreeType CI pipeline t=
o include Windows on ARM (ARM64) support. I wanted to ask whether setting u=
p a self-hosted Windows on ARM runner would make sense for more comprehensi=
ve testing and long-term stability.</div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Calibri, He=
lvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class=3D"elemen=
tToProof">
Adding Windows on ARM coverage in CI would help ensure consistent build and=
test validation on this platform. I=92d be happy to help contribute config=
uration changes if this direction seems reasonable.</div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Calibri, He=
lvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class=3D"elemen=
tToProof">
Thanks for your time.<br>
<br>
Regards,<br>
Harish</div>
</body>
</html>
--_000_MA5P287MB4625E7CBB2BFBA3AE5C9A0EA9EBBAMA5P287MB4625INDP_--