[Guide] New psptoolchain for Leopard and Tiger. (The proper way)
I have posted PSPSDK guides for Mac in the past, but the toolchain has changed a lot since my last guide. This guide will get the full SDK installed the way it should be done.
Yes, including PSPLink and Remotejoy :D
The 1st thing you will need is XCode 2.5 (Tiger) or XCode 3.0 (Leopard)
The 2nd thing you will need is MacPorts (OS X's native ports system)
MacPorts: Here for Leopard And Here for Tiger
Note: For XCode you will need to become a ADC Member (Free for XCode)
After XCode is installed, install MacPorts.
Now do the following:
Open your Terminal.app and run:
sudo port -d selfupdate
Now to setup your exports:
sudo port -v install autogen autoconf automake nano libtool libsdl patchutils subversion wget gmake
In the nano window past the following code:
ctr+x > y (for yes) > enter
Next setup your path that is needed:
sudo mkdir -p /usr/local/pspdev
Now to get the toolchain and do the proper setup:
sudo chmod a+rwx /usr/local/pspdev
Now for the OS X patches:
svn co svn://svn.ps2dev.org/psp/trunk/psptoolchain/ osx
Next a small libtool fix:
svn co http://svn2.assembla.com/svn/pspsdk/osx/
sudo ln -s /opt/local/bin/glibtoolize /opt/local/bin/libtoolize
Now we can start the SDK install:
sudo ln -s /opt/local/bin/glibtool /opt/local/bin/libtool
All done now I highly recommend you do the following:
svn co svn://svn.ps2dev.org/psp/trunk/psplibraries/
Like you can see this will install the most commonly used libs.
Next I think you should also do this:
'Make install" will fail, so do:
svn co svn://svn.ps2dev.org/psp/trunk/prxtool/
sudo cp prxtool /opt/local/bin
If you have DarwinPorts or MacPorts installed, and its broken somehow (getting non-fixable build errors), do this to uninstall:
Only do this if you get any build errors that can't be fixed.
sudo rm -rf /opt/local
If your running a Intel Mac I also recomend that you install wine.
It's free and can be useful for running some small windows apps ;)
sudo port -v install wine
Prism at ps2dev.org
UsefulIdiot at ps2dev.org
Without the info from them and some others I would not have been able to get this correct.