In order to install DevKitPro you need to download it, extract it and then run the installer. For some reason they decided to make the installation wizard come up twice, even though there is only one thing to be installed. Both times the wizard tells you that you have successfully installed DevKitPro. Only after you close the second wizard that the first wizard disappears and DevKitPro is actually installed. After that you can simply start the program DevKitPro.exe. A small window with a bar at the top of it will appear. Press the 'Tool Settings' button. The window will be divided into three sections, you're currently looking at the 'General' section. The 'General' section contains a list of settings. The settings themselves aren't that important, but you'll be able to see what's available for you to use with those settings when you get to the 'Tool Settings' window. The settings are similar to those in the 'General' window that you opened. In the 'General' window press the 'Application Settings' button. In the 'Application' section you should see the name of the compiler, DevKitARM, which you should be using. Press it. Then press the 'Tool Settings' button again. In the 'General' section there should be a checkbox next to 'Developer Environment'. Tick it. Press the 'Tool Settings' button again. The 'General' section will now contain some more details about the application. Press the 'Tool Settings' button again. Then press the 'Configure' button. DevKitPro will now ask you some questions, it's nothing to worry about, just answer them.
The first question will be whether DevKitPro should be run as an Administrator. Choose 'Yes'. If DevKitPro crashes now don't worry, it's perfectly normal. Just press the 'Cancel' button and then the 'Exit' button on the main screen of DevKitPro.
DevKitPro will now start to install the required software. If you have 'computername' of a computer you'd like to work on, simply press the 'OK' button on the main screen. If you don't want to install all the software you can press the 'Cancel' button.
You will notice that the devkitPro console shows errors. These are normal as devkitPro needs to interact with the system to do things. At the bottom of the screen you can click on the error and it will show you what the error is.
With all of this installed we can now start writing some code. I am going to be using the devkitPro version of the GameCube emulator for testing the Mario Kart DS homebrew due to it being completely different than the Nintendo GameCube emulator the Wii uses. You can also use the other emulators that devkitPro provides you with.
Some applications, such as Java, require that the application directories and libraries are updated to a newer version before the user can update. However, there are some applications that are not explicitly API-specific, such as the X Window System, the X server source code, are automatically updated as required.
If user is in the "nebula 3 pro torrent" group, this is the full name of the group to add the users.If user is not in "nebula 3 pro torrent" group, this is the full name of the group to add the users. 827ec27edc