Infrastructure changes for aarch64 packages

Jon Turney jon.turney@dronecode.org.uk
Sat Nov 14 19:13:37 GMT 2026


I've more or less come to the end of the list I wrote a couple of years 
ago, of changes needed in the packaging pipeline to support aarch64. To 
summarize:


* calm

calm now accepts arch-tagged packages in uploads.

uploaded source packages are moved to the path src/ (if not already 
there), avoiding the madness of duplicated (or possibly arch-distinct) 
source packages with the same name-version-release.

calm is now prepared to accept aarch64 uploads.

calm now generates a package manifest for aarch64.


* cygport

Package filenames are now arch-tagged.

cygport's existing cross-compilation support has been extended to add 
the aarch64 target, so if you have the cross-toolchain from [1], you 
could (theoretically) 'cygport --arch aarch64 foo.cygport all upload'

(Practically, this won't work because (i) the dependencies for foo are 
not yet available, and (ii) calm (correctly) refuses to allow you to 
upload a different source package (maybe just due to timestamps) with 
the same version-release identifier.)

Automatic dependency generation now also works when cross-building, when 
a suitable tool for querying packages installed into the cross-sysroot 
is available.


* scallywag

There's also now some (minimal) support using that to cross-build 
packages in scallywag.

(At the moment, this is gated by a whitelist, which allows scallywag to 
interpret ARCHES="all" as including aarch64. Only cygwin itself is on 
that whitelist currently. You can also force this for a single build by 
adding --push-option="aarch64".)

(I think I'd like to extend this to be more flexible so that troublesome 
packages, like e.g. rust, can be cross-built, but... maybe that's a 
project for next year...)

Given a suitable tool, the cygwin packages listed in BUILD_REQUIRES will 
be installed into the cross-sysroot.


* setup

Assuming you have a Windows 11 arrch64 machine, you can install aarch64 
packages using the x86_64 build [2] of the very latest cygwin setup 
(2.941), by providing the '--arch aarch64' option.



[1] https://cygwin.com/pipermail/cygwin-developers/2026-October/012847.html

[2] The deployed setup executable is cross built from Fedora. The 
necessary mingw-aarch64 toolchain doesn't exist there, so there is no 
aarch64 native build of setup.


I guess the next thing to work on will be gradually adding to the 
aarch64 whitelist, until we have the dependencies for a self-hosted 
compiler...


More information about the Cygwin-apps mailing list