A windows installer to do this automatically is now available.
First you need to obtain the relevant files for your chosen platform.
devkitARM, devkitPPC, devkitPSP, libnds, libmirko and libgba may be obtained from the sourceforge site.
In order to use a gcc based toolchain it is recommended that you have a unix style environment providing bash, make and some other tools found on that platform. devkitPro is not designed to work with cygwin and there are some peculiarities in using the toolchains with that environment. MinSys is the recommended alternative.
MinSys 1.0.10 (2,807,501 bytes).
A folder structure like this is recommended. The top "devkitPro" directory can be anywhere but should not have spaces in the path
- c:\devkitPro
- devkitARM
- devkitPPC
- devkitPSP
- msys
- libgba
- libmirko
- libnds
- Programmers Notepad
- c:\projects
- gamecube
- gba
- gp32
- nds
- psp
On linux/osx a similar layout is suggested but msys is not necessary (or available for that matter) and you should replace Programmer's Notepad with your editor of choice. The environment variables DEVKITPRO DEVKITARM, DEVKITPPC and DEVKITPSP should be added on those systems too - this allows the example projects to work without modification across all three platforms.
- /usr/local/devkitPro
- devkitARM
- devkitPPC
- devkitPSP
- libgba
- libmirko
- libnds
- ~/projects
- gamecube
- gba
- gp32
- nds
- psp
The MinSys package comes with it's own installer, you should select the appropriate path to install.
In windowsXP/2000 click Start->Settings->Control Panel, double click the System icon then select the advanced tab. You should see a dialog as shown here.
Look for path in the bottom section, highlight it and click the lower edit button. Add the path to your msys bin folder to the start of the path - the default is c:\msys\1.0\bin. You can also add the path to the toolchain binaries here - c:\devkitPro\devkitARM\bin, c:\devkitPro\devkitPSP\bin and/or c:\devkitPro\devkitPPC\bin. Adjust the example(s) to reflect your own setup and ensure there is a ';' character between each path entered.
Click New in the upper box to add new environment variables, you should get a box like this.
Add a variable for DEVKITPRO as shown, adjusting the path to suit your installation. You should note that these variables are for use by the makefiles running through msys and should be unix format paths, using /c/ rather than c:/. In the same manner add variables for DEVKITARM ( /c/devkitPro/devkitARM) and DEVKITPPC (/c/devkitPro/devkitPPC). On linux and OSX these should replace /c/ with /usr/local.
libgba, libnds and libmirko are distributed as .tar.bz2 archives and can be simply extracted to the appropriate place ( the top level directory as shown above - where DEVKITPRO is set) using WinRar or a similar program
You should also obtain a decent editor for writing code. The current recommendation is Programmer's NotePad
This package also comes with it's own installer, you should select the appropriate path to install.
Example code is now being released in stable tarballs which should be used in preference to the previous advice to use CVS. There have been numerous problems during toolchain updates when users update from CVS and find that the examples don't work due to requiring the latest iteration of the toolchain and libraries which may still be in testing.