Getting Started

Getting Started

Important

The currently documented end-to-end development baseline is Windows 11 x64. Linux and macOS are future native targets, not supported end-to-end workflows today.

Nakagawa Recomp is a developer-facing PSP static-recompilation project. Its deepest validation target is Hot Shots Tennis: Get a Grip, USA (UCUS-98701); the public repository is not an arbitrary-game launcher.

Supported baseline

Component	Current requirement
Host OS	Windows 11 x64
Shell	PowerShell 7.6+ (pwsh); Windows PowerShell 5.1 is not supported
Python	CPython 3.14.x
Compiler/build	MSYS2 UCRT64 GCC/G++ and GNU Make
Window/runtime	SDL3
Graphics	Current Vulkan SDK, Vulkan loader, and a Vulkan-capable GPU for the default renderer

Run the repository doctor before debugging a build:

python tools/hst_doctor.py --scope build

The setup guide is authoritative for discovery rules and package names. The optional Next.js dashboard is a separate project and is not required for the native runtime.

Quick path

flowchart LR
    A["1 · Clone public source"] --> B["2 · Install supported toolchain"]
    B --> C["3 · Run hst_doctor.py"]
    C --> D["4 · Prepare lawful local input"]
    D --> E["5 · BuildFull"]
    E --> F["6 · Verify and run"]

Loading

Step	Guide	Result
1–3 · Prepare	Clone the public repository, install the baseline above, and run the doctor.	Toolchain and dependency discovery are checked before compilation.
4 · Supply input	Follow docs/SETUP.md using only your own lawful local files.	Private title input stays in Git-ignored storage.
5 · Build	Run .\hst_manager.ps1 -Action BuildFull from PowerShell 7.6+.	Analysis and generated source are refreshed before native compilation.
6 · Interpret	Continue with Build and Run, then read Current Status.	A build result is separated from title, hardware, and release acceptance.

Public/private boundary

Public source contains	You provide locally
Recompiler/runtime source, tests, synthetic fixtures, public reference data, and audit tooling.	A lawful decrypted flat PSP executable plus any decrypted modules and extracted data required by the route.

Caution

Do not put ISOs, PBP files, firmware modules, keys, proprietary assets, generated retail-title C, private captures, or local paths into issues, pull requests, Wiki pages, or public research reports. If publication status is uncertain, keep the material private.

Generated translation units and executables are local build products. Their names and chunk count can change with the discovered function inventory; never edit generated C by hand.

What success means

A successful build means the documented pipeline completed for the selected local inputs and host toolchain. It does not prove PSP hardware equivalence, complete API coverage, general title support, or public fresh-machine release acceptance.

Missing inputs, an invalid Vulkan SDK, unsupported encrypted modules, or an HLE gap should remain visible as a diagnostic failure—not be hidden behind fabricated success.

Next: Build and Run → Repository Tour