1,310
edits
Difference between revisions of "Compiling ScummVM/RPI"
Compiling ScummVM/RPI (view source)
Revision as of 19:39, 13 December 2020
, 19:39, 13 December 2020→Installing the needed Raspberry Pi headers and libraries on PC: added libfribidi-dev and libglew-dev installation to apt-get
Praetorian (talk | contribs) (Edited commands to create a distribution folder rather than a scummvm binary only) |
Praetorian (talk | contribs) (→Installing the needed Raspberry Pi headers and libraries on PC: added libfribidi-dev and libglew-dev installation to apt-get) |
||
| Line 23: | Line 23: | ||
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 needs for its features and various game engines: | 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 needs for its features and various game engines: | ||
sudo apt-get update | sudo apt-get update | ||
sudo apt-get upgrade | sudo apt-get upgrade | ||
sudo apt-get install -y --no-install-recommends \ | 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 \ | |||
libfribidi-dev \ | |||
libglew-dev | |||
On the '''host PC''' we first export the path where we will copy these into, and then we manually copy them. One option (shown in the example commands below) is to copy the Raspberry Pi headers and libraries to ''/opt/rpi_root'', but any other path with the right permissions for our user (within common sense) should be ok: | On the '''host PC''' we first export the path where we will copy these into, and then we manually copy them. One option (shown in the example commands below) is to copy the Raspberry Pi headers and libraries to ''/opt/rpi_root'', but any other path with the right permissions for our user (within common sense) should be ok: | ||