The Nintendo Switch version of Starship is not compiled on the Switch itself — you build or download the PC release first to generate the required asset archives, then copy a small set of files to your SD card. A pre-built Switch package is also available from the nightly CI pipeline if you want to skip building from source entirely.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/HarbourMasters/Starship/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start (Pre-built Nightly)
If you do not want to build from source, download the latest Switch build directly from the nightly CI pipeline:This link always points to the most recent successful CI run from the
main branch.Generating Asset Archives on PC
The Switch build requires two.o2r asset archive files that are produced by running the PC version once. You can either build the PC release from source (see the Windows, Linux, or macOS guides) or download a PC release from the Releases page.
Run the PC release once
Launch the PC version of Starship (
starship.exe on Windows, starship.appimage on Linux, or Starship on macOS) and select your US 1.0 or US 1.1 ROM when prompted.The launcher will extract assets and write the following files to the same directory as the executable:sf64.o2r— game assets extracted from your ROMstarship.o2r— port-specific assets
Download the Switch NRO
Download the latest Switch package from the nightly link above (or from Releases) and extract the ZIP.The archive contains the
starship.nro homebrew binary.Copy files to your SD card
Copy all of the following files into a single folder on your Switch SD card (for example
sdmc:/switch/starship/):| File | Source |
|---|---|
starship.nro | Extracted from the Switch ZIP |
sf64.o2r | Generated by the PC release |
starship.o2r | Generated by the PC release |
CI Setup for Forks
Starship’s CI pipeline uses GitHub Actions. The Extract Assets step requires a self-hosted runner that has access to your ROM file. To configure this on your own fork:- Go to Settings → Actions → Runners in your GitHub repository.
- Add a new self-hosted runner and assign it the
asset-buildertag. - Follow GitHub’s documentation to configure the runner as a service.
Windows CI Runners
Linux / macOS CI Runners
Checkapt-deps.txt (Linux) or macports-deps.txt (macOS) in the repository root for the complete list of packages that must be pre-installed on your runner machine.