Getting Started/devkitPPC: Difference between revisions

From devkitPro
Jump to navigation Jump to search
No edit summary
(Redirected page to Getting Started)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
If your host platform is Windows then use the [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=160396 Windows Installer/Updater] package. Otherwise you may proceed with manual installation.
#REDIRECT [[Getting_Started]]
 
The first thing that you need to do is create a folder for the devkitPro toolchains. Start by opening a terminal - on OSX use the apple key + space, then type terminal. This command creates the new folder.
 
mkdir /opt/devkitpro
 
When we're done the layout for your devkitPro folder should end up like this, each folder links to the appropriate sourceforge package.
 
devkitpro
    |
    +-- [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=124208 devkitPPC]
    +-- examples
    |    |
    |    +-- [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=273807 gamecube]
    |    +-- [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=273886 wii]
    +-- [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=126925 libogc]
 
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.
 
The first package to install is the devkitPPC tarball, obtained from the [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=124208 devkitPPC] link shown above. Download the appropriate tarball for your host platform - the files are named as devkitPPC_<revision>-<processor>-<os>.tar.bz2. For OSX we provide universal binaries - devkitARM_<revision>-osx.tar.bz2.
 
Once the file is downloaded then you need to extract it into the devkitpro folder
 
cd /opt/devkitpro
tar -xvjf <file you downloaded>
 
Obviously replace <file you downloaded> with the name of the file obtained from sourceforge. On OSX you can simply drag & drop the downloaded file into the terminal window to get the file path.
 
Now you need to obtain the support libraries.
 
Download the latest binary of [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=126925 libogc] then create a new folder and extract the tarball from the terminal window as before. '''Note:''' This is the file without "-src-" in the name.
 
mkdir libogc
cd libogc
tar -xvjf <libogc tarball>
 
Again, replace <libogc tarball> with the name of the file obtained from sourceforge. On OSX you can simply drag & drop the downloaded file into the terminal window to get the file path.
 
Now download [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=197264 libfat-ogc].
 
tar -xvjf <libfat-ogc tarball>
 
Now all that remains are the examples archives. Move back to the devkitpro folder and create an examples/wii folder.
 
cd ..
mkdir -p examples/wii
 
Grab the [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=273886 wii examples] archive from sourceforge & extract it here.
 
tar -xvjf <examples tarball>
 
cd ..
mkdir -p examples/gamecube
 
Grab the [http://sourceforge.net/project/showfiles.php?group_id=114505&package_id=273807 gamecube examples] archive from sourceforge & extract it here.
 
tar -xvjf <examples tarball>
 
 
Add these variables in your execution environment, for instance, editing the .bashrc file located in your home folder:
 
export DEVKITPRO=/opt/devkitPro
export DEVKITPPC=$DEVKITPRO/devkitPPC

Latest revision as of 01:12, 6 June 2018

Redirect to: