Three more of the platforms #719 tracks, built the same way the .deb and AppImage workflows already are: version read from CHANGELOG, one job per platform, whatever built gets attached to the release and whatever did not is warned about by name. Windows.yml answers #709 by what it does NOT install. The report was that mingw-w64-x86_64-cegui is not available in MSYS2, which is true - it was dropped - but nothing needs to replace it: TSC has not needed a system CEGUI since 2024-10-04. It compiles CEGUI itself, statically, from the cegui submodule, applying cegui-cpp11.patch and cegui-cmake-policy.patch on the way, and mruby and pod-parser the same. So the dependency list leaves cegui and mruby out on purpose, and the 64-bit build goes through with MSYS2's UCRT64 SFML 3.0.2. The installer is CPack's NSIS one, which tsc/CMakeLists.txt already configures down to the installer icon and the desktop shortcut. The 32-bit job is kept and marked continue-on-error rather than deleted. MSYS2 ended 32-bit support in May 2024 and stopped building its mingw32 packages then - months before SFML 3 was released - so there is no 32-bit SFML 3 in MSYS2 and a 32-bit build of current TSC cannot be produced from it. That is a fact about MSYS2 rather than about TSC, and it should be a job whose log says so on every run rather than a platform that quietly vanished from the release. The way back, if 32-bit matters more than this, is building the dependency chain from source for i686 as the AppImage build already does for SFML. Mac.yml is #691 turned into something repeatable. That port was real work but what came out of it was a zip on a file-sharing site, and the experimental macOS support it produced is in the tree already. This builds on macos-13 (Intel), 14 and 15 (Apple silicon), sets CMAKE_OSX_DEPLOYMENT_TARGET two versions below each runner so the result runs on older macOS than it was built on, wraps the install tree in a TSC.app and ships a .dmg. A universal disk image needs both CPUs and cannot come from one job: Homebrew's libraries are built for the machine they are installed on, so CMAKE_OSX_ARCHITECTURES="x86_64;arm64" has nothing universal to link against. The two per-CPU builds are made first and lipo welds every Mach-O in the bundle together afterwards, which is what lipo is for. If one architecture failed there is nothing to weld, and the per-CPU images are published anyway. Flatpak.yml is #733, and it is two things. The single-file bundles go on the release. The repository - one OSTree repo holding both architectures, with a tsc.flatpakrepo beside it - is what makes `flatpak update` work instead of every update being a download by hand, and it is static files only, so the website can serve it with no server to run. It is unsigned; signing it needs a GPG key, which is a decision and a secret rather than something a workflow can invent, and the README in the repository says so. The manifest needed reviving first. It was written in 2018 against runtime 18.08: its boost came from bintray, which was shut down in 2021, and its SFML was 2.5.1, which the SFML 3 port no longer builds against - so it could not have built anything as it stood. It is on freedesktop 24.08 with a live boost URL and SFML 3.0.2 (both sha256 sums recomputed from the actual downloads), and its cegui and mruby modules are deleted, because TSC compiles both itself and building them into /app built something nothing used. Its rename-icon, rename-desktop-file and rename-appdata-file keys are gone too - they renamed tsc.* files that extras/ stopped producing when it was brought up to standard in #696; the installed names are org.secretchronicles.TSC.* now. NOT verified: none of these builds, which need a Windows runner, a Mac and a flatpak-builder - there is none of the three here. What was checked: that all five workflows are valid YAML and their matrices resolve; that the manifest is still valid JSON after the edit; that MSYS2 really does have SFML 3.0.2 and really has no cegui package, from packages.msys2.org; and that the two source archives the manifest now names download and hash to the sums written into it.

Uh oh!

Flatpak Version #733

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions