ppsspp

preserve-emulation/ppsspp

Fork 0

mirror of https://github.com/hrydgard/ppsspp.git synced 2026-09-30 08:16:38 +02:00

Files

T

History

Henrik RydgårdandClaude Opus 5 cf1d513c9e Don't default to building x64 on a machine that isn't

The MSBuild examples passed /p:Platform=x64 and the run lines pointed at
Windows/x64/..., so following them on an ARM64 machine produced an x64 build -
which then runs anyway under emulation, so nothing looks wrong. It is slower
than the native build, it isn't the code ARM users get, and a benchmark taken
from it measures the emulator: the colour conversion benchmark this was noticed
on reads 200 MPix/s emulated against 300 native.

The examples now say <platform> rather than either value, so there is no default
to follow and the machine has to be looked up. Also note that
$PROCESSOR_ARCHITECTURE describes the shell, not the host, and says AMD64 from
an emulated shell.

test.py searched only Windows\x64 for the headless binary, so on Windows-on-ARM
it would silently test an emulated build; it now looks for the native one first.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-18 11:38:49 -06:00

emu-api

Document and wrap the PPSSPP "emulator:" devctls (API for homebrew)

2026-08-24 10:46:04 +02:00

building.md

Don't default to building x64 on a machine that isn't

2026-09-18 11:38:49 -06:00

CodeWarriorMangling.md

docs: clarify that the destructor flag 0 vs -1 is a caller-side convention

2026-08-30 00:02:14 +02:00

command-line.md

Had Claude clean up its own notes.