Getting Started: Difference between revisions

From devkitPro
Jump to navigation Jump to search
(add linsk to sourceforge packages)
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 a toolchain binary is provided for your platform you can download and extract the tarball to the appropriate place. Previously we have been recommending /usr/local/devkitPro but have since learned that we should be installing in /opt/devkitpro.
For other platforms there are a few options available. Where a toolchain binary is provided for your platform you can download and extract the tarball to the appropriate place. Previously we have been recommending /usr/local/devkitPro but have since learned that we should be installing in /opt/devkitpro. Note: Most GUI based archive managers have trouble extracting the archives properly, you should use command line tar to work with them.  


Once you have the tarball extracted set the environment variables expected by the devkitPro build system. All the toolchains expect $DEVKITPRO to contain the path to the main folder where the tools and support libraries reside - that's /opt/devkitpro in the recommended configuration. Each toolchain also expects a variable pointing to it's location within that folder, $DEVKITARM will be /opt/devkitpro/devkitARM and $DEVKITPPC will be /opt/devkitpro/devkitPPC. Once you have the toolchain extracted and the environment variables set then installing the support libraries from source is a simple matter of make && make install.
Once you have the tarball extracted set the environment variables expected by the devkitPro build system. All the toolchains expect $DEVKITPRO to contain the path to the main folder where the tools and support libraries reside - that's /opt/devkitpro in the recommended configuration. Each toolchain also expects a variable pointing to it's location within that folder, $DEVKITARM will be /opt/devkitpro/devkitARM and $DEVKITPPC will be /opt/devkitpro/devkitPPC. Once you have the toolchain extracted and the environment variables set then installing the support libraries from source is a simple matter of make && make install.

Revision as of 01:32, 9 May 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 a toolchain binary is provided for your platform you can download and extract the tarball to the appropriate place. Previously we have been recommending /usr/local/devkitPro but have since learned that we should be installing in /opt/devkitpro. Note: Most GUI based archive managers have trouble extracting the archives properly, you should use command line tar to work with them.

Once you have the tarball extracted set the environment variables expected by the devkitPro build system. All the toolchains expect $DEVKITPRO to contain the path to the main folder where the tools and support libraries reside - that's /opt/devkitpro in the recommended configuration. Each toolchain also expects a variable pointing to it's location within that folder, $DEVKITARM will be /opt/devkitpro/devkitARM and $DEVKITPPC will be /opt/devkitpro/devkitPPC. Once you have the toolchain extracted and the environment variables set then installing the support libraries from source is a simple matter of make && make install.

All the packages are provided on the main Sourceforge download page, the stable release packages should be used in preference to CVS. While every effort is made to maintain CVS in a state where users can build the packages there are often phases where some packages are dependent on tools which are under test and not yet publically available.

Where a binary is not provided then users should use the most recent stable release of the buildscripts. Again 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.

There is also an experimental linux installer package linked in the forums. Linux devkitPSP binaries are not provided at this time.

We have several tarballs of example code available in the examples packages on sourceforge. These are also available through the Windows installer but will currently need to be downloaded manually for other platforms.

The recommended layout for your devkitPro folder should end up like this, each folder links to the appropriate sourceforge package.

devkitPro
   |
   +-- devkitARM
   +-- devkitPPC
   +-- devkitPSP
   +-- examples
         |
         +-- gamecube
         +-- gba
         +-- gp32
         +-- nds
         +-- wii
   +-- msys                ( windows only )
   +-- libgba
   +-- libmirko
   +-- libnds
   +-- libogc
   +-- Programmers Notepad ( windows only )

Nothing else should be placed inside these folders unless otherwise instructed by the devkitPro toolchain maintainers. On Windows several of these folders are removed and replaced by the update system.

Once you have your toolchain, support libraries and examples of choice installed then it's time to review the devkitPro build system