1,316
edits
Difference between revisions of "Compiling ScummVM/RPI"
Jump to navigation
Jump to search
→Installing the official Raspberry Pi cross-compiler on PC
Praetorian (talk | contribs) |
Praetorian (talk | contribs) |
||
| Line 11: | Line 11: | ||
Add it to the ''PATH'' environment variable so that we have the cross-compiler binaries available from our scummvm building directory. For example, if my Raspberry Pi ''tools'' repository ended cloned in ''tools'' under my ''home'' directory, I would do: | Add it to the ''PATH'' environment variable so that we have the cross-compiler binaries available from our scummvm building directory. For example, if my Raspberry Pi ''tools'' repository ended cloned in ''tools'' under my ''home'' directory, I would do: | ||
<nowiki>PATH=$PATH:$HOME/tools/arm-bcm2708/arm-linux-gnueabihf/bin</nowiki> | <nowiki>export PATH=$PATH:$HOME/tools/arm-bcm2708/arm-linux-gnueabihf/bin</nowiki> | ||
After adding the cross-compiler executables directory to ''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 have the cross-compiler installed and accessible. | After adding the cross-compiler executables directory to ''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 have the cross-compiler installed and accessible. | ||