Add arm64 linux

[ahoneybun]

This builds if you run the build.py file with the ARCH that matches your system enabled:

• Built x86_64 on a thelio-b1 locally
• Built aarch64 on a Pi 4B remotely and Astra locally
• Fix build.py to have a variable for the CI to call depending on the ARCH
• Update Github CI build the correct ARCH using the correct Runner.

This also updates the linuxdeploy-plugin-gtk.sh to match upstream as that builds for me locally using ./build.py --release.

[ahoneybun]

It looks like we have to add it to the org for us to use the Arm64 runners:

https://github.blog/changelog/2024-06-24-github-actions-ubuntu-24-04-image-now-available-for-arm64-runners/

https://github.com/actions/partner-runner-images?tab=readme-ov-file#available-images

[ids1024]

https://github.blog/changelog/2024-09-03-github-actions-arm64-linux-and-windows-runners-are-now-generally-available

Arm64 runners are available to customers on our Team and Enterprise Cloud plans.

The pop-os organization is currently on the free plan (plus LFS storage). So unless we change that, I think we'd need to either wait for it to be available their too, or do this a different way.

[ids1024]

Cross-compiling is easy with Rust, though the C library dependencies are a hassle. If pkg-config handles those fine though, it would work with an arm64 sysroot that has the necessary packages.

[ahoneybun]

We could build it with another CI to not need to be signed and just provide the hash I believe right?

[ids1024]

Yeah, that's also a possibility, if there are good alternatives. The AppImage isn't signed.

[ahoneybun]

@ids1024 sorry I meant to just put the arm64 AppImage in the Github release and link to it from the site since it isn't signed anyway. The CI is only really for making a release automatic.

[ids1024]

You mean building locally on an ARM64 system and add it to the release manually? Yeah, that should work too.

[ahoneybun]

I built the latest 1.3.12 release on an Astra yesterday which I can send over. If we want to add building that as a checkbox that could work and I would just remove my changes to the ci.yml file so this PR should pass.

[ids1024]

Yeah, merging any changes to the appimage build script and leaving CI unchanged for now would be good here.

It may not be that hard to set up a cross-compile build. I think I almost have that working after building an arm64 focal sysroot using debootstrap and setting some PKGCONFIG_ env vars...

[ahoneybun]

I've removed it for now and we can add it back later. Depending on the Github pricing we may want to look at this:

https://www.blacksmith.sh/blog/building-multi-platform-docker-images-for-arm64-in-github-actions

[ahoneybun]

It looks like we may be able to use the CI soon!

https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/

[ahoneybun]

So very close @ids1024 !

https://github.com/pop-os/keyboard-configurator/actions/runs/12845992865/job/35820656866?pr=247#step:4:444

[ahoneybun]

Well after running it again it works now!

[ahoneybun]

I rebased on master with the Windows fix and all the CI are passing now!

[ids1024]

The upload-to-release Github Actions job also needs to be updated for this to be automatically added to a release. Should be sufficient to copy the x86_64 linux section there, and change to aarch64.

Otherwise, the linux/build.rs and CI changes look good.

I rebased on master with the Windows fix and all the CI are passing now!

Looks like you did a cherry-pick instead of a rebase? It should be rebased, and squashed into one or two commits. But doing a squash merge may amount to the same thing.

[ahoneybun]

I don't think the upload-to-release will run with a PR like this until there is a new version right?

Yea looks like GH's default is to "Squash and merge" which should fix it up.

[ids1024]

Looks good now. (As long as it's merged with a squash merge.)

[leviport]

This only touches build scripts and CI seems happy, so I think that's sufficient.