Setting up Development Environment: Difference between revisions
Undo revision 20670 by LinkSoraZelda (talk) The link is not dead, it definitely works. The edit makes it prone to becoming outdated, only the newest version of the script should be used. |
mNo edit summary |
||
(8 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
= Setup = | = Setup = | ||
Install [https://devkitpro.org/ devkitARM]. If it's already installed, update it using sudo (dkp-)pacman -Syu. On Windows, there's a [https://github.com/devkitPro/installer/releases/latest graphical installer]. On Unix-like platforms such as Linux/macOS, there's [https://github.com/devkitPro/pacman/releases/latest pacman].. | |||
==Windows== | ==Windows== | ||
devkitPro | * If you already use msys2 then you can follow the instructions at https://github.com/devkitPro/pacman/releases/latest to add the devkitPro repositories. | ||
* [https://github.com/devkitPro/installer/releases/latest download the latest version of the graphical installer] from | |||
Otherwise | |||
* [https://github.com/devkitPro/installer/releases/latest download the latest version of the graphical installer] from github and run it, following the instructions as you go. | |||
* An Internet connection is required. | * An Internet connection is required. | ||
* | * Ensure at least "3DS Development" is ticked - you can also leave the other options ticked if you wish. | ||
* Once the installer has finished, launch MSYS from: | * Once the installer has finished, launch MSYS from: | ||
** Windows 7 and earlier: Start -> All Programs -> devkitPro -> MSYS | ** Windows 7 and earlier: Start -> All Programs -> devkitPro -> MSYS | ||
Line 19: | Line 19: | ||
==Unix-like platforms== | ==Unix-like platforms== | ||
Currently devkitPro provides precompiled versions of devkitARM for the following Unix-like platforms: Linux ( | Currently devkitPro provides precompiled versions of devkitARM for the following Unix-like platforms: Linux (x86_64), macOS (x86_64). Note that Linux x86_64 binaries are usable under WSL. | ||
* | * Follow the instructions to install pacman found at https://github.com/devkitPro/pacman/releases/latest | ||
* run sudo (dkp-)pacman -S 3ds-dev to install the tools and libraries for 3ds development | |||
* logout and login again to get the environment settings needed. | |||
= Building the examples = | = Building the examples = | ||
3DS examples are still being created; however, there are a growing number of examples available from the [https://github.com/devkitPro/3ds-examples devkitPro/3ds-examples GitHub repository]. | 3DS examples are still being created; however, there are a growing number of examples available from the [https://github.com/devkitPro/3ds-examples devkitPro/3ds-examples GitHub repository]. These are downloaded by the installer and can be found in $DEVKITPRO/examples/3ds | ||
These can be built from the command line. | These can be built from the command line. | ||
Line 61: | Line 39: | ||
==Running your code== | ==Running your code== | ||
To run it on your 3DS, start the Homebrew Launcher, press Y to open the network loader, then on your PC type: <code>$ | To run it on your 3DS, start the Homebrew Launcher, press Y to open the network loader, then on your PC type: <code>$DEVKITPRO/tools/bin/3dslink '''my3dsproject'''.3dsx</code>, replacing '''my3dsproject''' with the name of the 3dsx file you want to run.) | ||
If all goes well, you'll soon see your application running on your 3DS. If not, it could help to add <code>-a '''ipaddress'''</code>, replacing '''ipaddress''' with the ip address of the console (visible on homebrew launcher after pressing Y). | |||
= Troubleshooting = | = Troubleshooting = | ||
'''I get the "Please set DEVKITARM in your environment." error.''' | '''I get the "Please set DEVKITARM in your environment." error.''' | ||
Ensure you have the devkit-env package installed - (dkp-)pacman -Sl | grep devkit-env. Logout and login to get the enviroment settings. | |||
For WSL users, you need to close the Bash shell, then reopen it for WSL to reload all of the variables from a clean state. | For WSL users, you need to close the Bash shell, then reopen it for WSL to reload all of the variables from a clean state. |