A packaging release. No runtime or lifter behaviour changes — the same tree
as v0.9.0, plus the CI and release plumbing that makes it downloadable.
Downloads
| Bundle | Contents |
|---|---|
ps3recomp-v0.9.1-win-x64.zip |
ps3recomp_runtime.lib |
ps3recomp-v0.9.1-mac-arm64.zip |
libps3recomp_runtime.a (arm64) |
Each bundle carries the static runtime library, its public headers
(include/ps3emu), the full Python recompilation pipeline (tools/), and the
docs. Verify against SHA256SUMS.txt.
Windows and macOS only: those are the two platforms with CI proving they
compile. Shipping an untested Linux binary would repeat the mistake this
release series started by fixing. macOS still cannot run a recompiled game —
the PPU boot scaffold is Win32-only.
What changed
- Releases now ship binaries. A
v*tag builds a bundle per platform and
attaches it with checksums. v0.9.0 was source-only, so trying the project
meant reproducing the whole toolchain setup (clang-cl + Ninja under vcvars)
first.lib/andinclude/come from the project's own install rules, so a
bundle cannot drift from what a localcmake --installproduces. - The test suites re-run in the release job. A tag can point at any commit,
including one that never went through CI. Without this, "downloaded from a
release" would mean less than "green on master". Every bundle here was built
from a tree that passed 1311 conformance checks and all eight suites on both
platforms. - Windows CI. The macOS job guarded the POSIX paths, but nothing guarded the
platform everything actually ships on — a change made to satisfy Clang could
have broken the clang-cl build with nobody noticing until someone tried to
build a port. - Docs point at ReXGlue for the Xbox 360
side rather than a tool collection of our own.
Full notes for the substantive work — the Metal backend, the first CI, and the
fifteen VMX miscompiles it uncovered — are in
v0.9.0.