Releases & packaging
Here’s how a version of Rondelek gets from a tag to something a family can
download. The short story: you push a v* tag, and
.github/workflows/release.yml does the rest.
| Job | Runner | Produces |
|---|---|---|
desktop | windows-latest | rondelek-<tag>-x86_64-pc-windows-msvc.zip (both .exes) |
linux | ubuntu-22.04 | rondelek-<tag>-x86_64.AppImage + .zsync, rondelek-<tag>-x86_64-unknown-linux-gnu.tar.gz |
publish | ubuntu-latest | attaches every build job’s files to the GitHub Release |
The build jobs only upload workflow artifacts. publish is the one job that
touches the release itself, so two jobs never race each other to create it. It
runs on !cancelled(), which means one platform failing doesn’t stop the
others from shipping. The macOS legs are commented out in the matrix for now.
Two binaries travel together
Every package holds both rondelek and rondelek-game, side by side, and they
need each other. The app starts a game by running the game binary from its own
folder (App::spawn_game, which uses std::env::current_exe()). If you’re
curious why the game is a separate process at all, Architecture
explains.
The Linux AppImage
Everything for the AppImage lives in packaging/appimage/, which also has its
own README. Here’s what you’ll find there:
AppRunruns the app by default, or the game on its own with--game(or when it’s invoked through a symlink namedrondelek-game).rondelek.desktopis the menu entry. ItsStartupWMClass=rondelekmatches the app’s window id (with_app_id("rondelek")inapp/src/main.rs).build.shassembles the AppDir from two release binaries and runs appimagetool (static type2 runtime, zstd, with update information for zsync-based updates).smoke.shruns the finished AppImage on a virtual display and checks that the app and the game each manage to render a frame.
The job runs on ubuntu-22.04 on purpose. A binary needs at least the glibc it was built against, and 2.35 covers Ubuntu 22.04+, Debian 12+ and current rolling distros. Nothing else is bundled besides the two binaries: X11/Wayland/GL come from the host at runtime.
The icon
assets/icon/rondelek.png (512×512) is generated by cargo run --bin genicon,
using the same pixel-art engine as the banner. Both binaries embed it as their
window icon, and the AppImage uses it as its icon too.