Getting Started: Difference between revisions
Wintermute (talk | contribs) No edit summary |
Wintermute (talk | contribs) No edit summary |
||
Line 3: | Line 3: | ||
For those of you who wish to install offline a "Download only" option is provided to download the packages without installing for later installation on another machine. This is best used by running the installer from a removable drive where it will store the downloaded packages. The "Download and install/install from downloaded files" option will pick up the packages from the directory the installer is running from. | For those of you who wish to install offline a "Download only" option is provided to download the packages without installing for later installation on another machine. This is best used by running the installer from a removable drive where it will store the downloaded packages. The "Download and install/install from downloaded files" option will pick up the packages from the directory the installer is running from. | ||
For other platforms there are a few options available. Where | For other platforms there are a few options available. Where possible you should stick to the binary distributions - building from source can be a path of frustration even for seasoned developers. The following pages cover each toolchain in detail. | ||
[[Getting_Started/devkitARM | Manual instructions for installing devkitARM]] | |||
[[Getting_Started/devkitPPC | Manual instructions for installing devkitPPC]] | |||
Where a binary is not provided then | Where a binary is not provided then you should use the most recent stable release of the [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=124206 buildscripts]. CVS should be avoided since the buildscripts found there will often contain the next iteration of a given toolchain rather than the current stable release. Using these scripts is a simple matter of extracting the archive, running ./build-devkit.sh from a bash shell and following the prompts. The scripts will also build and install the current support libraries from the release tarballs. | ||
Revision as of 16:28, 22 June 2008
For Windows users getting started with devkitPro toolchains is made easy by the convenient Windows Installer/Updater package. It is strongly recommended that windows users stick with this rather than attempting to set up the packages manually. The updater handles all the sticky little details of installation required for properly functioning toolchains. This is a web based installer so please ensure that you have a net connection, your Internet Explorer proxy settings are correct and that any firewall software you have installed allows the application to access the net.
For those of you who wish to install offline a "Download only" option is provided to download the packages without installing for later installation on another machine. This is best used by running the installer from a removable drive where it will store the downloaded packages. The "Download and install/install from downloaded files" option will pick up the packages from the directory the installer is running from.
For other platforms there are a few options available. Where possible you should stick to the binary distributions - building from source can be a path of frustration even for seasoned developers. The following pages cover each toolchain in detail.
Manual instructions for installing devkitARM
Manual instructions for installing devkitPPC
Where a binary is not provided then you should use the most recent stable release of the buildscripts. CVS should be avoided since the buildscripts found there will often contain the next iteration of a given toolchain rather than the current stable release. Using these scripts is a simple matter of extracting the archive, running ./build-devkit.sh from a bash shell and following the prompts. The scripts will also build and install the current support libraries from the release tarballs.