45
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: − − * We can set the DEVKITPRO environment variable first so the script knows where to install or we can set the variable later to the value the script tells us. The script will default this to ~/devkitPro − <pre> − echo "export DEVKITPRO=/opt/devkitpro" >> ~/.bashrc − source ~/.bashrc − </pre> Line 35:
Line 29: − + − +
Setting up Development Environment (view source)
Revision as of 23:45, 24 March 2018
, 23:45, 24 March 2018→Unix-like platforms
** Arch Linux/ALWSL: <code>sudo pacman -S git curl wget</code>
** Arch Linux/ALWSL: <code>sudo pacman -S git curl wget</code>
** macOS: Download Git from [http://git-scm.com/download/mac] and install it. Curl is included with the OS.
** macOS: Download Git from [http://git-scm.com/download/mac] and install it. Curl is included with the OS.
* Next, we need to download, make executable and run the devkitARM updater (don't worry, the updater is also the installer.)
* Next, we need to download, make executable and run the devkitARM updater (don't worry, the updater is also the installer.)
curl -L https://raw.githubusercontent.com/devkitPro/installer/master/perl/devkitA64update.pl -o devkitA64update.pl
curl -L https://raw.githubusercontent.com/devkitPro/installer/master/perl/devkitA64update.pl -o devkitA64update.pl
chmod +x ./devkitA64update.pl
chmod +x ./devkitA64update.pl
./devkitA64update.pl /opt/devkitpro
./devkitA64update.pl
</pre>
</pre>
You may need to use sudo here if you set DEVKITPRO to a path not writable by your user.
You can either use sudo here or chown /opt/devkitpro to be writable by your user before running the script.
= Building the examples =
= Building the examples =