Difference between revisions of "Compiling ScummVM/RPI"

Jump to navigation Jump to search
Line 17: Line 17:
== Installing the needed Raspberry Pi headers and libraries on PC ==
== Installing the needed Raspberry Pi headers and libraries on PC ==


We need to copy over the /usr, /lib and /opt directories from your Raspbian SD to your PC (the computer were you will do the cross-compilation), for the needed headers and libs to be available.  
We need to copy over the '''/usr''', '''/lib''' and '''/opt''' directories from your Raspbian SD Card to your host PC (the computer were you will do the cross-compilation) for the needed headers and libraries to be available.
Of course, you'll have to install any additonal libs from Raspbian running of the Pi before expecting them to be available, so if you compile scummvm with FLAC support, you should have installed the libflac development libs on the Pi first.
 
Of course, first you'll have to install any additional libraries from Raspbian running on the Pi before expecting them to be available so, if you want compile ScummVM with FLAC support, you should have installed the libflac development libraries on the Pi beforehand.
 
As an example, on the Raspberry Pi running Raspbian (Buster) OS 3.2 (January 2020) we can execute the following to install third party libraries that ScummVM features and game engines need:
 
<nowiki>
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install -y --no-install-recommends \
            libsdl2-dev \
            liba52-0.7.4-dev \
            libjpeg62-turbo-dev \
            libmpeg2-4-dev \
            libogg-dev \
            libvorbis-dev \
            libflac-dev \
            libmad0-dev \
            libpng-dev \
            libtheora-dev \
            libfaad-dev \
            libfluidsynth-dev \
            libfreetype6-dev \
            libcurl4-openssl-dev  \
            libsdl2-net-dev \
            libspeechd-dev \
            zlib1g-dev
</nowiki>


First we export the path where we will copy these into, and then we will manually copy them. I choose /opt/rpi_root, but any other path with the right permissions for your user and common sense is going to be ok:
First we export the path where we will copy these into, and then we will manually copy them. I choose /opt/rpi_root, but any other path with the right permissions for your user and common sense is going to be ok:


<nowiki>
mkdir -p /opt/rpi_root
mkdir -p /opt/rpi_root
export RPI_ROOT=/opt/rpi_root
export RPI_ROOT=/opt/rpi_root
cd <SD_mountpoint_directory>
cd <SD_mountpoint_directory>
cp -R usr lib opt $RPI_ROOT
cp -R usr lib opt $RPI_ROOT
</nowiki>


== Configuring ScummVM ==
== Configuring ScummVM ==
547

edits

Navigation menu