Repository files navigation

• PSPDEV
  • Table of Contents
  • Up and running
  • What these scripts do
  • Requirements
  • Installation from source
  • Docker generation
  • Extra steps
    • macOS
    • Local package builds
  • Thanks

You can get started very quickly by grabbing the latest development pre-releases from thereleases' page for your platform and extract them to thepspdev directory in yourpath.

Export thePSPDEV environment variable to point to thepspdev directory. For example:

export PSPDEV=~/pspdevexport PATH=$PATH:$PSPDEV/bin

These scripts download (git clone) and install:

• psptoolchain
• pspsdk
• psp-packages
• psplinkusb
• ebootsigner

• Installgcc/clang,make,cmake,patch,git,texinfo,flex,bison,gettext,wget,gsl,gmp,mpfr,mpc,libusb,readline,libarchive,gpgme,bash,openssl andlibtool.
• If you don't have those.We offer a script to help you for installing dependencies:

sudo ./prepare.sh

1. Ensure that you have enough permissions for managing PSPDEV location (default to/usr/local/pspdev, but you can use a different path). PSPDEV location MUST NOT have spaces or special characters in its path! PSPDEV should be an absolute path. On Unix systems, if the commandmkdir -p $PSPDEV fails for you, you can set access for the current user by running commands:

   export PSPDEV=/usr/local/pspdevsudo mkdir -p$PSPDEVsudo chown -R$USER:$PSPDEV

2. Add this to your login script (example:~/.bash_profile)

   export PSPDEV=/usr/local/pspdevexport PATH=$PATH:$PSPDEV/bin

   NOTE: Ensure that you have full access to the PSPDEV path. You can change the PSPDEV path with the following requirements:Only use absolute paths,Do not use spaces.,Only use Latin characters.

3. Run build-all.sh

   ./build-all.sh

sudo rm -rf$PSPDEV

This repo also uses CI/CD to create a docker image calledpspdev/pspdev:latest per change. This is useful if you're a developer that wants to create/port an application to the PSP. You can compile your project using this docker image.

If you want, you canJUST install the extra dependencies aspsplinkusb and ebootsigner. To achieve this execute

./build-extra.sh

If you download the pre-built macOS binaries and get a security error such as"pspsh" cannot be opened because the developer cannot be verified., you can remove the quarantine attribute by running:

xattr -dr com.apple.quarantine path/to/prebuilt/pspdev

The toolchain (binutils, gcc), the SDK (pspsdk) and the host tools are built locally. However, the provided packages (psp-packages) are installed viapsp-pacman (or a similar mechanism if not available), which fetches packages fromGitHub releases. If you wish to build these packages locally, you might define the variableLOCAL_PACKAGE_BUILD which will force pacman to build the packages from source instead of downloading them:

LOCAL_PACKAGE_BUILD=1 ./build-all.sh

This is particularly useful if you are testing changes in the toolchain (i.e. gcc or binutils) and want to test your changes end to end. It can also be useful if you want a hermetic build and don't want to use any of the provided binaries.

Special thanks to all the contributors and maintainers whose efforts and commitment drive the continuous improvement of this project.