mrkeyoor.comAsk

boykopovar/AnyPS5tested 03 Oct 2026commit ccd60ce

AnyPS5 review

AnyPS5 is worth evaluating for relinker and system-library research.

  • Install 14 s
9/145passed, run exited non-zero
  • Build failed
Dev Toolsevaluationupdated 24 Oct 2026
+5,115stars / 7d

AnyPS5 is a relinker and replacement system-library project for porting PS5 executables to native desktop formats. Its README describes this as conversion without emulation or a separate runtime process. Building the converter, building the libraries and running a converted game are separate tasks.

Verdict

AnyPS5 is worth evaluating for relinker and system-library research. Our October 3, 2026 run at ccd60ce completed configuration but stopped during compilation; the subsequent CTest summary includes tests that did not run. That result limits what this review can confirm and does not prove the current product is broken. For playing a particular PS5 game, check the project's current per-title reports before committing to setup. Neither the historical README example nor this sandbox run establishes broad compatibility.

We ran it

Lab card: what happened when we ran AnyPS5
Lab card from our sandbox run
Screenshot of AnyPS5 (github.com/boykopovar/AnyPS5)
github.com/boykopovar/AnyPS5
Install✓ · 14s
Build✗ · 44s
Tests✗ · 1s9 passed · 136 failed of 145 (ctest)
Repo10465 files~2,300,908 lines of source · 222 MB · 9 CI workflows

Answers from our run

Does AnyPS5 build from source?

Dependencies installed in 14 seconds, and the build failed. We cloned commit ccd60ce into a clean Debian container with 3 CPUs and no project-specific setup.

Do AnyPS5's tests pass?

No. The project's own test command finished in 1 seconds and reported 9 passed, 136 failed (ctest).

Who should not use AnyPS5?

Players choosing software on the assumption of broad PS5 game compatibility: the supplied evidence does not establish that coverage.

What are the alternatives to AnyPS5?

shadPS4, Kyty. AnyPS5 is worth evaluating for relinker and system-library research.

Setup2/5The October 3, 2026 run at ccd60ce completed configuration but failed compilation. Current relinker-only instructions offer a smaller setup path that we have not executed; no working installed CLI was verified.
Docs4/5The build guide distinguishes conversion from runtime libraries and documents toolchains, test registration and troubleshooting. The technical-debt page retains a narrower Windows requirement than the build guide.
Community2/5The v0.1.1 release credits multiple contributors. Supplied evidence does not measure support responsiveness, sustained participation or adoption; stars and an open-PR count are not used as quality evidence.
Maturity2/5Current documentation requires per-title compatibility checks, and technical debt identifies unverified runtime behavior. Our historical incomplete build cannot establish current reliability or general game compatibility.

Discussed on

  1. hnAnyPS5: Port PS5 binaries to PC without emulation (87% system libraries mapped)375 points
  2. hnANYPS5 Runs PS5 Games Natively on PC – No Emulation Required3 points

Who it’s for

C++ contributors researching executable conversion and replacement PS5 system libraries.
Developers who want to build the relinker separately before attempting the full runtime.
Preservation researchers prepared to investigate per-title behavior and use binaries obtained in accordance with applicable laws and licenses.

Who it’s NOT for

Players choosing software on the assumption of broad PS5 game compatibility: the supplied evidence does not establish that coverage.
Readers who need this review to confirm a working installed CLI or a playable game: our recorded run established neither.
Developers expecting a macOS relinker build to include the system libraries needed to run converted games.
Contributors who cannot investigate build or runtime failures beyond the documented setup.

Setup reality

In our recorded run on October 3, 2026, at commit ccd60ce (full SHA ccd60ce0ca364ce26a0cccfb73223c9e2a1c4312), the harness's install step completed in 14 seconds. Its tail shows a dependency download, CMake configuration and generated build files. This establishes configuration completion, not installation or verification of a working CLI.

The build exited 1 after 44 seconds. The compiler reported that clock_cast was not a member of std::chrono in the save-data implementation. CTest subsequently exited 8; the harness recorded approximately 1 second. Its summary recorded 9 passed and 136 failed out of 145, but the raw tail includes numerous Not Run entries. The 136 figure therefore must not be read as 136 executed assertions failing. These are recorded summary counts after an incomplete build, without complete-log reconciliation or verified exhaustive unique coverage.

The current build guide documents a separate relinker-only mode requiring CMake, a C++20 compiler and a build tool. Python 3.9 or newer enables its Python regression tests. This mode supports Linux, Windows and macOS, including Apple silicon, but does not build the system libraries. The full build has additional dependencies and target-specific requirements. We have not executed these current instructions.

Decide what you need to build

AnyPS5 separates executable conversion from the libraries needed to run converted software. That distinction matters when deciding whether to try it: a successful relinker build would establish a conversion tool, not a working game runtime.

The current README describes a relinker that converts executables to native formats and replacement system PRX libraries for dynamic linking, without emulation or a separate runtime process. Those are the project's architectural claims. Our run did not verify converted-game execution.

What our recorded run establishes

Our run began on October 3, 2026, at 22:10:35.646 UTC, using commit ccd60ce0ca364ce26a0cccfb73223c9e2a1c4312. The recorded configuration was 3 CPUs, 8 GB of memory and image lab-cpp:1. The image label alone does not establish the operating-system or compiler version.

The harness labeled its first step install. It completed in 14 seconds, with download progress followed by CMake's configuration and generation messages. There is no installed-binary check in the supplied record. Calling this a successful CLI installation would overstate the evidence.

The build exited 1 after 44 seconds. At line 143 of the save-data implementation, the compiler rejected this expression:

std::chrono::clock_cast<std::chrono::system_clock>(written)

The diagnostic says that clock_cast is not a member of std::chrono. Ninja stopped after a subcommand failed. The supplied tail does not establish the compiler version or a verified remedy.

CTest then exited 8. The harness rounded its duration to 1 second; CTest's own tail reports 0.16 seconds of real test time. The recorded summary is 9 passed and 136 failed out of 145. However, the same tail marks many entries Not Run, including guest_addresses, guest_memory and strict_nid_filter. Other entries, such as elf_offsets and input_magic, are marked Failed.

These results describe an unsuccessful test command after an incomplete build. They do not establish 136 executed test failures or 136 independent product defects. The supplied counts have not been reconciled against a complete log to verify exhaustive unique coverage. No game conversion, game workload, frame-rate benchmark or current-version retest is recorded.

The repository scan recorded 10,465 files, approximately 2,300,908 source lines, 222 MB and 9 CI workflow files. It did not detect a Dockerfile or a top-level tests directory. That directory signal does not mean the project lacks tests: the recorded CTest run and build paths show tests elsewhere in the repository.

Current setup offers a smaller starting point

The build guide now documents a relinker-only build without submodules, SDL, Vulkan, FFmpeg, FreeType or the shader recompiler. It requires CMake, a C++20 compiler and a build tool. Python 3.9 or newer enables Python regression tests and must be discovered during configuration for those tests to be registered.

The guide says this mode builds on Linux, Windows and macOS, including Apple silicon. Its output is x86-64: Linux ELF by default, Windows PE with --windows, or Mach-O with --macos. The conversion host and execution host are separate considerations. Relinker-only mode does not build system libraries, and the guide says release libraries are supplied for Linux and Windows only. Converted games still need target-OS libraries and a compatible x86-64 host.

The full build requires x86-64, Git, CMake 3.22.1 or newer, Ninja, C++20 and recursive submodules. Linux uses GCC, G++ and binutils, with additional display and audio development dependencies described in the guide. FFmpeg binaries download during configuration unless FFMPEG_PREBUILT_DIR is supplied.

Windows full builds are no longer documented as limited to one package. The guide describes the required POSIX threads and exception support, naming WinLibs GCC 15.2.0 and MSYS2 UCRT64 GCC 16.2.0-6 as toolchain examples. It separately explains why Scoop's standalone GCC 15.2.0 cannot build the runtime. The technical-debt page still names the older specific MinGW-w64 GCC 15.2.0 requirement; follow the more detailed build guide when selecting a toolchain.

With the default BUILD_TESTING=OFF, the full build's default target does not produce the PRX libraries; the explicit libs target is required. On Windows, the guide also requires libgcc_s_seh-1.dll, libstdc++-6.dll and libwinpthread-1.dll beside the patched libraries. These instructions are source documentation, not steps we completed in a new run.

Compatibility needs a per-title answer

The README pinned to our measured commit reports Dreaming Sarah running at a stable 60 fps on a GTX 1050 Ti and i5-7500 3.4GHz. That is an upstream report, not our benchmark, and it does not establish compatibility for other games.

The current README directs readers to Game bring-up discussions for per-game status and test reports. The former compatibility-document URL was inaccessible in the supplied source collection. That does not prove its historical contents were false, but it prevents using that page to assert a current one-game total or current Windows and Linux results.

The README also defines its system-library progress percentage as the share of functions known to the project, not every PS5 system function. It is not a percentage of games that work.

The technical-debt document identifies concrete remaining uncertainty. Guest-module trampolines under --to-intel have synthetic relinker-test coverage but no verified game title on Linux or Windows. Some exports have unknown or assumed signatures, and several cancellation behaviors remain unverified. These are useful boundaries for research, not evidence that every title encounters the same failure.

How to choose your next step

For conversion research, start with the documented relinker-only mode, confirm which tests were registered and inspect the result on a compatible host. For runtime research, use a separate full-build directory, build the libraries and check a current report for the exact title you intend to investigate. We have not verified either path beyond the historical run described above.

For PS4 emulation, shadPS4 is a relevant alternative. Its README describes an early PS4 emulator and directs end users to QtLauncher. Kyty is relevant for studying an early emulator that reports simple PS4 games and PS5 homebrew. Neither description makes it a general replacement for AnyPS5's PS5 conversion work.

What the scores mean

These are editorial suitability ratings, not benchmark results. The scale is 1 for a substantial observed barrier, 2 for limited supporting evidence, 3 for a documented path with material verification gaps, 4 for detailed supporting documentation or validation within the assessed scope, and 5 for comprehensive evidence across that scope. Unknown adoption, compatibility and support quality earn no extra credit.

Setup receives 2/5 because our historical build stopped, while current documentation offers a smaller path we have not tested. Documentation receives 4/5 for its detailed separation of build modes, toolchains, library targets and troubleshooting, with a conflicting Windows requirement remaining in the debt page. Community receives 2/5 because the v0.1.1 release credits multiple contributors, but the supplied evidence does not establish support responsiveness or adoption. Maturity receives 2/5 because compatibility remains title-specific and the debt document records unverified runtime behavior. The v0.1.1 release is a historical source, not proof that it is the latest release.

The earlier AnyPS5 announcement covers the project's initial attention and compatibility report. This review answers the practical setup question: which component do you need, and what does the available evidence actually confirm?

Alternatives

ProjectWhat it isPick it when
shadPS4 gh↗An early PlayStation 4 emulator for Windows, Linux and macOS.Choose it for PS4 emulation rather than PS5 executable conversion. Its README directs end users to QtLauncher and its game compatibility information; this is not a substitute for PS5 support.
KytyAn early PS4 and PS5 emulator whose README reports some simple PS4 games and PS5 homebrew.Choose it to study an emulator approach to simple PS4 software or PS5 homebrew. Its README warns of glitches, crashes, freezes and low FPS, so it does not establish broad PS5 game compatibility.

What people are saying

  1. [github-trending] boykopovar/AnyPS5

Sources

  1. AnyPS5 README
  2. AnyPS5 build guide
  3. AnyPS5 compatibility list
  4. AnyPS5 technical debt
  5. AnyPS5 v0.1.1 release

More dev tools reviews