Open main menu

Difference between revisions of "Compiling ScummVM/RPI"

2 bytes removed ,  22:06, 15 February 2016
Line 10: Line 10:
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 tools at my home directory, I would do:


PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf/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 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.
25

edits