mirror of
https://github.com/mihawk-99/PS5_RetroArch.git
synced 2026-10-18 23:09:29 -05:00
Mihawk
fe174f8f85
The route is now: prove the whole console path with a complete known-good title, then replace its sources with a fresh RetroArch. This lands the first half. Building it needed four things, each found by a failed build and none of them a change to its sources: - the project's own vendored SDK rather than the one in $HOME; - PS5_CLANG=/usr/bin/clang, because its wrapper defaults to a clang-18 that is not installed, while the sibling project that works uses plain clang; - a minimal documented jsonschema stand-in at tooling/pystub/, because mbedTLS regenerates a source file with a script that imports it and the package is not installed. The stand-in validates the schema features that script uses and raises otherwise, so a malformed data file still fails loudly; - a verified runtime/libc.prx. The project ships only its manifest; the boilerplate's copy carries the same digest, so it was used. All four are captured in tools/build-native-app.sh. Evidence: make app completed and the converter's inspector reports "container: signed, plaintext", twelve segments, integrity valid for dist/PPSA99002/eboot.bin; the folder is staged at handoff/PPSA99002/. Not proven: that it runs. Placement is the console owner's step, since writes from this machine do not reach the console's title folders, and a title must also be registered with the shell before a launch is anything but "is not registered".