Multi-arch on workflows

[KaruroChori]

In an ideal scenario the build process for vs should work on most architecture, so in addition to amd64, arm32, aarch64 and riscv64 should also be tracked.
I have no plan to directly support building from systems which are not a modern linux distro like ubuntu 24.04, debian trixie or the freedesktop 24.08 of flatpak.
Still, macos13 and macos14 both might just work out of the box, so it might make sense not to ignore them on purpose.

Any other target is just meant to be cross-compiled. So testing workflows for vs should be based on cross-compiled artifacts I guess. This would include tests for platforms like win32 and win64.

[andy5995]

This is how I usually do multi-arch docker builds. They could then be used for testing in the CI. https://github.com/andy5995/gh-action-build-deb/blob/67848234988615f73d34e252089e7c44c2336dff/.github/workflows/docker.yml#L25

[KaruroChori]

Thanks, I am going to use that as reference :).

[andy5995]

Native arm64 builds can be done using Cirrus CI and Circle CI. I've been using Cirrus for a while. Curl used to use it. They switched to Circle CI. I set up a project on Circle CI but during the setup of my first project it glitched. Stuck at a "setting up" message for hours.

[andy5995]

For testing on *BSD without using Cirrus or CircleCI

https://github.com/vmactions
https://github.com/cross-platform-actions/action

[KaruroChori]

That would require me to set up accounts or something like that right? Are they external runners?
I missed the without.

[andy5995]

No and no.