Difference between revisions of "Compiling ScummVM/RPI"

Jump to navigation Jump to search
44 bytes removed ,  17:04, 18 October 2015
Line 5: Line 5:
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:


git clone git://github.com/raspberrypi/tools.git
git clone https://github.com/raspberrypi/tools.git
It will get cloned to a directory called tools at your current location.


It will get cloned to a directory called raspberrypi at your current location.
Add it to the path so we have the crosscompiler binaries available from our scummvm building directory. If my raspberrry pi tools repository ended cloned in tools at my home directory, I would do:


Add it to the path so we have the crosscompiler binaries available from our scummvm building directory. If my raspberrry pi tools repository ended cloned in raspberrrypi at my home directory, I would do:
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin


PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin
After adding the crosscompiler executables directory to the path, we should be able to run bcm2708hardfp-gcc, bcm2708hardfp-g++, etc... just try. They should yield an error because you pass them no input files, but that's expected. It's just a test so we know we've the crosscompiler installed and accesible.
 
After adding the crosscompiler executables directory to the path, we should be able to run arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, etc... just try. They should yield an error because you pass them no input files, but that's expected. It's just a test so we know we've the crosscompiler installed and accesible.


== Installing the needed Raspberry Pi headers and libraries on PC ==
== Installing the needed Raspberry Pi headers and libraries on PC ==
25

edits

Navigation menu