mirror of
https://github.com/ARMSX2/ARMSX2.git
synced 2026-08-24 16:50:16 -07:00
Brian Degenhardt
737966bbad
Both jobs have been in build-all.yml since it was written, so they build and get artifact-uploaded on every push, but neither was ever added to nightly.yml. The result is that the RetroArch core and the bare-kmsdrm handheld frontend are the two targets with no published download at all, which is backwards: those users are the least likely to build from source. Wire both into the nightly with the same inputs build-all.yml passes, and collect their .tar.zst into the release. Non-blocking, like the mobile jobs: publish's guard names only the PC jobs, so a failure here costs the asset rather than the release. Unlike the mobile jobs they cannot be marked continue-on-error, since that key is not permitted on a job that uses a reusable workflow, so a failure will still redden the run. That matches how they already behave in build-all.yml. Both build at OVERRIDE_HOST_PAGE_SIZE=4096, so the release notes say so. Neither is packaged as an AppImage on purpose: the AppImage runtime wants FUSE, and a bare-display handheld is exactly where that cannot be assumed. package-sdl.sh already bundles the libs it built and points the rpath at $ORIGIN/lib, so the tarball is self-contained without it.