Add SDL3 to CI and upload build artifacts

[thatcosmonaut]

It would be nice to figure out how to spit out a universal dylib for MacOS, but I'm not familiar enough with how that works. It would also be nice to figure out how to upload the release artifacts to the release page automatically when a release is tagged, but I'm not sure how to test that.

[flibitijibibo]

In addition to macOS we also need a Rocky 8 VM for Linux builds - we should ask Misa about this.

[thatcosmonaut]

Something like this? https://www.claudiokuenzler.com/blog/1381/how-to-run-github-ci-cd-workflows-actions-rocky-linux

[flibitijibibo]

Oh, that looks a lot easier than what I remember... yeah, if that works with 8 then we can integrate that and the output binaries should be good to go.

[flibitijibibo]

Output looks okay, so the final checklist:

• MinGW (see comment)
• Rocky Linux 8 x86_64
• Rocky Linux 8 aarch64

[thatcosmonaut]

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

We expect to begin offering Arm runners for open source projects by the end of the year.

Once this is enabled we can do the aarch builds. Working on the other stuff now.

[flibitijibibo]

For MinGW, do the Rocky tools include mingw32-cmake and mingw64-cmake? That'll help eliminate the toolchain files if so.

[flibitijibibo]

A few fixes here and there for the Rocky config - if this all works then the toolchain files can be deleted. We should also chrpath -d the Linux binaries, and possibly strip -S as well (not sure why this changes the Release binaries, but it does...)

[thatcosmonaut]

Rocky builds should be good now, it would be nice to spit out a universal MacOS dylib but I'm not gonna have time to work on that until next week at least.

[flibitijibibo]

Latest should be good as long as macOS cooperates...