You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: basic_programs.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -379,7 +379,7 @@ Documentation for SDL2_ttf can be found <a href="https://wiki.libsdl.org/SDL2_tt
379
379
## More Examples
380
380
{: .fs-6 .fw-700 }
381
381
382
-
More examples on how to use specific functions offered in the PSPDEV toolchain can be found [here](https://github.com/pspdev/pspsdk/tree/master/src/samples). Additional documentation on these functions can be found [here](https://pspdev.github.io/pspsdk/).
382
+
More examples on how to use specific functions offered in the PSP SDK can be found [here](https://github.com/pspdev/pspsdk/tree/master/src/samples). Additional documentation on these functions can be found [here](https://pspdev.github.io/pspsdk/).
Copy file name to clipboardExpand all lines: contributing.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Pull requests are always welcome!
24
24
## Where can I find the code?
25
25
{: .fs-6 .fw-700 }
26
26
27
-
The PSPDEV toolchain is build using quite a few different repositories which each add their own piece to the system. If you just want to build everything at once, the [pspdev repository](https://github.com/pspdev/pspdev) is the place to go.
27
+
The PSP SDK is build using quite a few different repositories which each add their own piece to the system. If you just want to build everything at once, the [pspdev repository](https://github.com/pspdev/pspdev) is the place to go.
28
28
29
29
There are automated builds, which build each part individually if there are changes. Here is a basic image showing the build order:
Copy file name to clipboardExpand all lines: debugging.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ The information received from `psp-addr2line` will be limited and not always use
81
81
## Using a Debugger
82
82
{: .fs-6 .fw-700 }
83
83
84
-
When using `psp-addr2line` is not enough to figure out what is going on, the best way to debug will be by using an actual debugger called GDB, which comes bundled with the PSPDEV toolchain as the `psp-gdb` command. PSPLINK allows this debugger to connect directly to the PSP.
84
+
When using `psp-addr2line` is not enough to figure out what is going on, the best way to debug will be by using an actual debugger called GDB, which comes bundled with the PSP SDK as the `psp-gdb` command. PSPLINK allows this debugger to connect directly to the PSP.
Copy file name to clipboardExpand all lines: downloads.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ nav_order: 7
7
7
# Downloads
8
8
{: .fs-8 .fw-700 .text-center }
9
9
10
-
Download the latest update for the PSPDEV toolchain here. If you don't have it setup yet, go to the [installation instructions](installation.html) instead! Otherwise click on the link for your system:
10
+
Download the latest update for the PSP SDK here. If you don't have it setup yet, go to the [installation instructions](installation.html) instead! Otherwise click on the link for your system:
Copy file name to clipboardExpand all lines: how_to_use.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ nav_order: 3
7
7
# How to use
8
8
{: .fs-8 .fw-700 .text-center }
9
9
10
-
This page will describe how to use the PSPDEV toolchain to build a basic program for the Playstation Portable (PSP), including screenshots. The screenshots will mainly be for Windows users, but the steps will not be much different for other operating systems, so you should be able to follow along.
10
+
This page will describe how to use the PSP SDK to build a basic program for the Playstation Portable (PSP), including screenshots. The screenshots will mainly be for Windows users, but the steps will not be much different for other operating systems, so you should be able to follow along.
11
11
12
12
Before going through this guide, make sure to have followed the [installation instructions](installation.html) first.
13
13
@@ -67,7 +67,7 @@ For building, a terminal is used with a couple of short commands. To open a term
67
67
68
68

69
69
70
-
This will open a terminal at the bottom of the screen. On Windows, this will be a powershell window, but the PSPDEV toolchain is installed in WSL. To open a WSL terminal instead, click on the arrow next to the `+` sign at the right side an select `Ubuntu (WSL)`:
70
+
This will open a terminal at the bottom of the screen. On Windows, this will be a powershell window, but the PSP SDK is installed in WSL. To open a WSL terminal instead, click on the arrow next to the `+` sign at the right side an select `Ubuntu (WSL)`:
Copy file name to clipboardExpand all lines: installation/docker.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ nav_exclude: true
10
10
## Docker
11
11
{: .fs-6 .fw-700 }
12
12
13
-
Docker can be used on almost every platform and offers and easy way to use the PSPDEV toolchain with very little setup.
13
+
Docker can be used on almost every platform and offers and easy way to use the PSP SDK with very little setup.
14
14
15
15
To use it, install Docker itself using the instructions [here](https://docs.docker.com/engine/install/).
16
16
@@ -31,4 +31,4 @@ docker run -ti -v .:/source pspdev/pspdev:latest
31
31
32
32
After that you can run `cd /source` to navigate to the code.
33
33
34
-
That's it, now the PSPDEV toolchain can be used to build PSP software. Check out the [Basic Programs](../basic_programs.html) page to for examples on what you can do with it.
34
+
That's it, now the PSP SDK can be used to build PSP software. Check out the [Basic Programs](../basic_programs.html) page to for examples on what you can do with it.
Installing the PSPDEV toolchain itself can be done with the following steps:
22
+
Installing the PSP SDK itself can be done with the following steps:
23
23
24
24
1. Download [the latest version of the toolchain here](https://github.com/pspdev/pspdev/releases/latest/download/pspdev-fedora-latest.tar.gz).
25
25
2. Extract the downloaded archive into your home directory, resulting in `/home/YOURUSERNAME/pspdev` being created.
@@ -39,4 +39,4 @@ Installing the PSPDEV toolchain itself can be done with the following steps:
39
39
psp-config --pspdev-path
40
40
```
41
41
42
-
That's it, now the PSPDEV toolchain can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
42
+
That's it, now the PSP SDK can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
Installing the PSPDEV toolchain itself can be done with the following steps:
24
+
Installing the PSP SDK itself can be done with the following steps:
25
25
26
26
1. Download the latest version of the toolchain for your system here:
27
27
-[arm64](https://github.com/pspdev/pspdev/releases/latest/download/pspdev-macos-latest-arm64.tar.gz) for M1 or newer CPUs.
@@ -47,4 +47,4 @@ Installing the PSPDEV toolchain itself can be done with the following steps:
47
47
psp-config --pspdev-path
48
48
```
49
49
50
-
That's it, now the PSPDEV toolchain can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
50
+
That's it, now the PSP SDK can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
Installing the PSPDEV toolchain itself can be done with the following steps:
26
+
Installing the PSP SDK itself can be done with the following steps:
27
27
28
28
1. Download [the latest version of the toolchain here](https://github.com/pspdev/pspdev/releases/latest/download/pspdev-ubuntu-latest-x86_64.tar.gz).
29
29
2. Extract the downloaded archive into your home directory, resulting in `/home/YOURUSERNAME/pspdev` being created.
@@ -43,4 +43,4 @@ Installing the PSPDEV toolchain itself can be done with the following steps:
43
43
psp-config --pspdev-path
44
44
```
45
45
46
-
That's it, now the PSPDEV toolchain can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
46
+
That's it, now the PSP SDK can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
Copy file name to clipboardExpand all lines: installation/windows.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ nav_exclude: true
10
10
## Windows Subsystem for Linux (WSL)
11
11
{: .fs-6 .fw-700 }
12
12
13
-
On Windows the PSPDEV toolchain is run on Ubuntu running on Microsoft's WSL. This is very easy to set up and will offer us the full power of Linux from a Windows machine.
13
+
On Windows the PSP SDK is run on Ubuntu running on Microsoft's WSL. This is very easy to set up and will offer us the full power of Linux from a Windows machine.
14
14
15
15
To set up WSL with Ubuntu in it run the following commands in a Powershell window started as administrator (right click run as administrator on Powershell in the start menu):
16
16
@@ -31,7 +31,7 @@ This can be useful when building a specific project.
31
31
## Dependencies
32
32
{: .fs-6 .fw-700 }
33
33
34
-
The PSPDEV toolchain requires a couple of dependencies to be installed before use. To install them, run the following command from an Ubuntu terminal:
34
+
The PSP SDK requires a couple of dependencies to be installed before use. To install them, run the following command from an Ubuntu terminal:
Installing the PSPDEV toolchain itself can be done with the following steps:
47
+
Installing the PSP SDK itself can be done with the following steps:
48
48
49
49
1. In a fresh WSL Session download the Toolchain Archive using the following command:
50
50
```shell
@@ -69,6 +69,6 @@ Installing the PSPDEV toolchain itself can be done with the following steps:
69
69
```shell
70
70
psp-config --pspdev-path
71
71
```
72
-
If everything is set up correctly, the path of the PSPDEV toolchain installation will be shown.
72
+
If everything is set up correctly, the path of the PSP SDK installation will be shown.
73
73
74
-
That's it, now the PSPDEV toolchain can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
74
+
That's it, now the PSP SDK can be used to build PSP software. Check out the [How to Use](../how_to_use.html) page for a guide on how to do so.
Copy file name to clipboardExpand all lines: tips_tricks.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Here some useful tips for developing for the PSP.
12
12
## Making Programs Work on Unmodded PSPs
13
13
{: .fs-6 .fw-700 }
14
14
15
-
The PSPDEV toolchain contains tools for making your program work on unmodded PSPs. This can be done by running psp-cmake with some additional commands when building like so:
15
+
The PSP SDK contains tools for making your program work on unmodded PSPs. This can be done by running psp-cmake with some additional commands when building like so:
16
16
17
17
```shell
18
18
mkdir build &&cd build
@@ -43,7 +43,7 @@ This makes sure that the other systems supported by the program keeps working th
43
43
## Managing Libraries
44
44
{: .fs-6 .fw-700 }
45
45
46
-
There are many C and C++ libraries available within the PSPDEV toolchain and most of them will be installed by default. Libraries are where most of the updates within the toolchain happen and they can be updated manually without redownload the toolchain using `psp-pacman`.
46
+
There are many C and C++ libraries available within the PSP SDK and most of them will be installed by default. Libraries are where most of the updates within the SDK happen and they can be updated manually without redownload the SDK using `psp-pacman`.
47
47
48
48
Updating the libraries installed can be done with the following command:
49
49
@@ -68,9 +68,9 @@ psp-pacman -S library
68
68
## Managing Licenses
69
69
{: .fs-6 .fw-700 }
70
70
71
-
Every project made with the PSPDEV toolchain will import at least some libraries, each with their own license. Everything bundled is free to use, but some libraries will ask you to share their license with your project or in rare cases give users access to your code to respect their licenses. The `psp-create-license-directory` tool can be used to easily collect the licenses that apply to your project, so you can comply with them and ship them with your project.
71
+
Every project made with the PSP SDK will import at least some libraries, each with their own license. Everything bundled is free to use, but some libraries will ask you to share their license with your project or in rare cases give users access to your code to respect their licenses. The `psp-create-license-directory` tool can be used to easily collect the licenses that apply to your project, so you can comply with them and ship them with your project.
72
72
73
-
To create a directory with a copy of the licenses that are always used in project made with the PSPDEV toolchain use the following command:
73
+
To create a directory with a copy of the licenses that are always used in project made with the PSP SDK use the following command:
74
74
75
75
```
76
76
psp-create-license-directory
@@ -91,6 +91,6 @@ psp-create-license-directory -l
91
91
## Updating the Toolchain
92
92
{: .fs-6 .fw-700 }
93
93
94
-
A new version of the PSPDEV toolchain is released at least once a month, so updating should be done regularly if you want to benefit from new features and bug fixes.
94
+
A new version of the PSP SDK is released at least once a month, so updating should be done regularly if you want to benefit from new features and bug fixes.
95
95
96
-
To update the toolchain, simply follow the installation instruction for your system on the [Installation](installation.html) page. Installing the dependencies can be skipped.
96
+
To update the SDK, simply follow the installation instruction for your system on the [Installation](installation.html) page. Installing the dependencies can be skipped.
0 commit comments