1,310
edits
Difference between revisions of "Compiling ScummVM/RPI"
→Configuring ScummVM
Praetorian (talk | contribs) |
Praetorian (talk | contribs) |
||
| Line 57: | Line 57: | ||
Now we configure scummvm buildsystem so it knows what backend we want and where is our raspberry pi local sysroot living, containing the Raspberry Pi headers and libs the cross-compiler and linker will need. In this example configuration, we disable additional libs, and debug symbols since it's intended for final users. | Now we configure scummvm buildsystem so it knows what backend we want and where is our raspberry pi local sysroot living, containing the Raspberry Pi headers and libs the cross-compiler and linker will need. In this example configuration, we disable additional libs, and debug symbols since it's intended for final users. | ||
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr | <nowiki> | ||
PKG_CONFIG_SYSROOT_DIR=$RPI_ROOT PKG_CONFIG_LIBDIR=$RPI_ROOT/usr/lib/arm-linux-gnueabihf/pkgconfig ./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --with-png-prefix=$RPI_ROOT/usr --disable-debug --enable-release</nowiki> | |||
Remember you should have exported the RPI_ROOT enviroment variable previously. | Remember you should have exported the RPI_ROOT enviroment variable previously. | ||
On the | On the Raspberry Pi, SDL2 will always be used since it provides graphics acceleration. | ||
''Note:'' If you are building ScummVM on your | '''Note:''' If you are building ScummVM directly on your Raspberry Pi itself, you might run out of memory during the final linking process of the build. If you use GNU ''ld'' for compiling, you could execute the following before running ''configure'': | ||
<nowiki>export LDFLAGS="-Wl,--no-keep-memory</nowiki> | |||
This tells GNU ''ld'' to optimize for memory usage. | |||
== Compiling ScummVM == | == Compiling ScummVM == | ||