https://wiki.scummvm.org/api.php?action=feedcontributions&user=Vanfanel&feedformat=atomScummVM :: Wiki - User contributions [en]2024-03-29T09:37:00ZUser contributionsMediaWiki 1.36.0https://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=22288Compiling ScummVM/RPI2016-02-15T22:34:41Z<p>Vanfanel: /* Installing the official Raspberry Pi cross-compiler on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx support, we would pass the --enable-dispmanx parameter to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
Remember you should have exported the RPI_ROOT enviroment variable previously.<br />
On the raspberrypi host, SDL2 will be always used since it provides graphics acceleration.<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=22287Compiling ScummVM/RPI2016-02-15T22:06:53Z<p>Vanfanel: /* Installing the official Raspberry Pi cross-compiler on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx support, we would pass the --enable-dispmanx parameter to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
Remember you should have exported the RPI_ROOT enviroment variable previously.<br />
On the raspberrypi host, SDL2 will be always used since it provides graphics acceleration.<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21899Compiling ScummVM/RPI2015-12-04T16:04:24Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx support, we would pass the --enable-dispmanx parameter to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
Remember you should have exported the RPI_ROOT enviroment variable previously.<br />
On the raspberrypi host, SDL2 will be always used since it provides graphics acceleration.<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21898Compiling ScummVM/RPI2015-12-04T16:03:11Z<p>Vanfanel: /* Installing the needed Raspberry Pi headers and libraries on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx support, we would pass the --enable-dispmanx parameter to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --enable-dispmanx --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
Remember you should have exported the RPI_ROOT enviroment variable previously.<br />
Also, these instructions can be used to cross-build a basic version with not dispmanx support if we don't pass the --enable-dispmanx parameter.<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21816Compiling ScummVM/RPI2015-10-18T17:20:45Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx support, we would pass the --enable-dispmanx parameter to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --enable-dispmanx --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
Remember you should have exported the RPI_ROOT enviroment variable previously.<br />
Also, these instructions can be used to cross-build a basic version with not dispmanx support if we don't pass the --enable-dispmanx parameter.<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21815Compiling ScummVM/RPI2015-10-18T17:19:42Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx support, we would pass the --enable-dispmanx parameter to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --enable-dispmanx --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
Remember you should have exported the RPI_ROOT enviroment variable previously.<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21814Compiling ScummVM/RPI2015-10-18T17:14:46Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --enable-dispmanx --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
Remember you should have exported the RPI_ROOT enviroment variable previously.<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21813Compiling ScummVM/RPI2015-10-18T17:12:39Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build scummvm with dispmanx support enabled:<br />
<br />
./configure --host=raspberrypi --enable-dispmanx --with-sdl-prefix=$RPI_ROOT/usr --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac --disable-mad --disable-vorbis --disable-tremor --disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21812Compiling ScummVM/RPI2015-10-18T17:06:02Z<p>Vanfanel: /* Installing the needed Raspberry Pi headers and libraries on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
cd <SD_mountpoint_directory><br />
<br />
cp -R usr lib opt $RPI_ROOT<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21811Compiling ScummVM/RPI2015-10-18T17:04:05Z<p>Vanfanel: /* Installing the official Raspberry Pi cross-compiler on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone https://github.com/raspberrypi/tools.git<br />
It will get cloned to a directory called tools at your current location.<br />
<br />
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:<br />
<br />
PATH=$PATH:$HOME/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin<br />
<br />
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.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/usr $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/lib $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/opt $RPI_ROOT<br />
<br />
Now we need to setup the cross-building sdl-config so it's used instead on the host system's sdl-config script. Edit $RPI_ROOT/usr/bin/sdl-config and change the prefix line to:<br />
<br />
prefix=$RPI_ROOT/usr<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21779Compiling ScummVM/RPI2015-07-22T10:48:16Z<p>Vanfanel: /* Installing the needed Raspberry Pi headers and libraries on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
mkdir -p /opt/rpi_root<br />
<br />
export RPI_ROOT=/opt/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/usr $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/lib $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/opt $RPI_ROOT<br />
<br />
Now we need to setup the cross-building sdl-config so it's used instead on the host system's sdl-config script. Edit $RPI_ROOT/usr/bin/sdl-config and change the prefix line to:<br />
<br />
prefix=$RPI_ROOT/usr<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21778Compiling ScummVM/RPI2015-07-22T10:26:15Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
RPI_ROOT=/opt/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/usr $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/lib $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/opt $RPI_ROOT<br />
<br />
Now we need to setup the cross-building sdl-config so it's used instead on the host system's sdl-config script. Edit $RPI_ROOT/usr/bin/sdl-config and change the prefix line to:<br />
<br />
prefix=/opt/rpi-root/usr<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOT/usr --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21777Compiling ScummVM/RPI2015-07-22T10:24:15Z<p>Vanfanel: /* Installing the needed Raspberry Pi headers and libraries on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
RPI_ROOT=/opt/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/usr $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/lib $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/opt $RPI_ROOT<br />
<br />
Now we need to setup the cross-building sdl-config so it's used instead on the host system's sdl-config script. Edit $RPI_ROOT/usr/bin/sdl-config and change the prefix line to:<br />
<br />
prefix=/opt/rpi-root/usr<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOTDIR/usr --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21776Compiling ScummVM/RPI2015-07-22T10:24:02Z<p>Vanfanel: /* Installing the needed Raspberry Pi headers and libraries on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
RPI_ROOT /opt/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/usr $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/lib $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/opt $RPI_ROOT<br />
<br />
Now we need to setup the cross-building sdl-config so it's used instead on the host system's sdl-config script. Edit $RPI_ROOT/usr/bin/sdl-config and change the prefix line to:<br />
<br />
prefix=/opt/rpi-root/usr<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOTDIR/usr --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21775Compiling ScummVM/RPI2015-07-22T10:23:31Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
export $RPI_ROOT /opt/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/usr $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/lib $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/opt $RPI_ROOT<br />
<br />
Now we need to setup the cross-building sdl-config so it's used instead on the host system's sdl-config script. Edit $RPI_ROOT/usr/bin/sdl-config and change the prefix line to:<br />
<br />
prefix=/opt/rpi-root/usr<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
./configure --host=raspberrypi --with-sdl-prefix=$RPI_ROOTDIR/usr --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21774Compiling ScummVM/RPI2015-07-22T10:21:57Z<p>Vanfanel: /* Installing the needed Raspberry Pi headers and libraries on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
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:<br />
<br />
export $RPI_ROOT /opt/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/usr $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/lib $RPI_ROOT<br />
<br />
cp -R <SD_mountpoint_directory>/opt $RPI_ROOT<br />
<br />
Now we need to setup the cross-building sdl-config so it's used instead on the host system's sdl-config script. Edit $RPI_ROOT/usr/bin/sdl-config and change the prefix line to:<br />
<br />
prefix=/opt/rpi-root/usr<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
RPI_ROOTDIR="/home/manuel/rpi_root" ./configure --host=raspberrypi --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21773Compiling ScummVM/RPI2015-07-22T10:10:48Z<p>Vanfanel: /* Installing the official Raspberry Pi cross-compiler on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:$HOME/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
So let's go with the headers and libs copy. I copied them to /home/manuel/rpi_root:<br />
<br />
cp -R <SD_mountpoint_directory>/usr /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/lib /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/opt /home/manuel/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
RPI_ROOTDIR="/home/manuel/rpi_root" ./configure --host=raspberrypi --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21749Compiling ScummVM/RPI2015-07-07T09:21:52Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:/home/manuel/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
So let's go with the headers and libs copy. I copied them to /home/manuel/rpi_root:<br />
<br />
cp -R <SD_mountpoint_directory>/usr /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/lib /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/opt /home/manuel/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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.<br />
<br />
Depending on whether we want dispmanx or GLES support, we would pass --enable-dispmanx or --enable-gles-rpi parameters to the configure script.<br />
For example, we would run configure like this to build a dispmanx version:<br />
<br />
RPI_ROOTDIR="/home/manuel/rpi_root" ./configure --host=raspberrypi --enable-dispmanx --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21661Compiling ScummVM/RPI2015-05-28T19:30:01Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:/home/manuel/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
So let's go with the headers and libs copy. I copied them to /home/manuel/rpi_root:<br />
<br />
cp -R <SD_mountpoint_directory>/usr /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/lib /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/opt /home/manuel/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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:<br />
<br />
RPI_ROOTDIR="/home/manuel/rpi_root" ./configure --host=raspberrypi --enable-gles-rpi --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac<br />
--disable-mad --disable-vorbis --disable-tremor<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21660Compiling ScummVM/RPI2015-05-28T19:29:27Z<p>Vanfanel: /* Configuring ScummVM */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:/home/manuel/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
So let's go with the headers and libs copy. I copied them to /home/manuel/rpi_root:<br />
<br />
cp -R <SD_mountpoint_directory>/usr /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/lib /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/opt /home/manuel/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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:<br />
<br />
RPI_ROOTDIR="/home/manuel/rpi_root" ./configure --host=raspberrypi --enable-gles-rpi --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac \<br />
--disable-mad --disable-vorbis --disable-tremor \<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21617Compiling ScummVM/RPI2015-03-21T19:05:30Z<p>Vanfanel: /* Installing the needed Raspberry Pi headers and libraries on PC */</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:/home/manuel/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
So let's go with the headers and libs copy. I copied them to /home/manuel/rpi_root:<br />
<br />
cp -R <SD_mountpoint_directory>/usr /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/lib /home/manuel/rpi_root<br />
<br />
cp -R <SD_mountpoint_directory>/opt /home/manuel/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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:<br />
<br />
RPI_ROOTDIR="/home/manuel/rpi_root" ./configure --backend=raspberrypi --host=raspberrypi --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac \<br />
--disable-mad --disable-vorbis --disable-tremor \<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM&diff=21616Compiling ScummVM2015-03-21T19:03:12Z<p>Vanfanel: /* Compiling ScummVM */</p>
<hr />
<div>{{Languages}}<br />
=== Compiling ScummVM ===<br />
<br />
ScummVM is written in C++ and has been ported to several different [[Platforms]]. Compilation of ScummVM is a bit different for each platform, so instructions have been included for the official platforms that ScummVM can be compiled for.<br />
<br />
{| border="1" cellpadding="2"<br />
|- style="background:silver"<br />
|Platform||Compiling instructions<br />
|-<br />
|[http://www.microsoft.com Windows] || [[Compiling ScummVM/Visual Studio|Visual Studio (MSVC)]], [[Compiling_ScummVM/MinGW|MinGW]] and [[Compiling ScummVM/DevCPP|Dev-C++]] instructions<br />
|-<br />
|[http://www.linux.org Linux] || [[Compiling ScummVM/GCC|GCC]]<br />
|-<br />
|[http://os4.hyperion-entertainment.biz/ AmigaOS4] || [[Compiling ScummVM/AmigaOS4|AmigaOS4]]<br />
|-<br />
|[http://www.microsoft.com/windowsmobile/ Windows CE/Mobile] || [[Compiling_ScummVM/Windows_CE|Windows CE]] instructions<br />
|-<br />
|[http://www.sega.jp/dc/ Sega Dreamcast] || [[Compiling ScummVM/Dreamcast|Dreamcast]] instructions<br />
|-<br />
|[http://www.us.playstation.com/PSP Sony PlayStation Portable]||[[Compiling ScummVM/PlayStation Portable|PlayStation Portable]] instructions<br />
|-<br />
|[http://www.us.playstation.com/PS2 Sony PlayStation 2]||[[Compiling ScummVM/PlayStation 2|PlayStation 2]] instructions<br />
|-<br />
|[http://us.playstation.com/ps3/ Sony PlayStation 3]||[[PlayStation_3#Building_from_source|PlayStation 3]] instructions<br />
|-<br />
|[http://www.apple.com/macosx/ Mac OS X]||[[Compiling ScummVM/Mac OS X|Mac OS X]] instructions (see also [[Compiling ScummVM/Mac OS X Crosscompiling|Mac OS X Crosscompiling]] and [[Compiling ScummVM/Mac OS X 10.2.8|Mac OS X 10.2.8]] instructions)<br />
|-<br />
|[http://www.apple.com/iphone/ Apple iPhone]||[[Compiling ScummVM/iPhone|iPhone]] instructions<br />
|-<br />
|[http://www.nintendo.com/ds Nintendo DS]||[[Compiling ScummVM/Nintendo DS|Nintendo DS]] instructions<br />
|-<br />
|[http://www.symbian.com/ Symbian]||[[Compiling ScummVM/Symbian|Symbian]] instructions<br />
|-<br />
|[http://wiki.sparemint.org/index.php/FreeMiNT Atari/FreeMiNT]||[[Compiling ScummVM/Atari/FreeMiNT|Atari/FreeMiNT]]<br />
|-<br />
|[http://en.wikipedia.org/wiki/BeOS BeOS]/[http://www.zeta-os.com/ ZETA]/[http://www.haiku-os.org/ Haiku]||[[Compiling ScummVM/BeOS/ZETA/Haiku|BeOS/ZETA/Haiku]] instructions<br />
|-<br />
|[http://www.nintendo.com/wii Nintendo Wii and Gamecube]||[[Compiling ScummVM/Wii|Wii and Gamecube]] instructions<br />
|-<br />
|[http://www.android.com/ Google Android]||[[Compiling ScummVM/Android|Android]] instructions<br />
|-<br />
|[https://developer.palm.com/ HP webOS]||[[Compiling ScummVM/WebOS|WebOS]] instructions<br />
|-<br />
|[http://www.maemo.org/ Maemo]||[[Compiling ScummVM/Maemo|Maemo]] instructions<br />
|-<br />
|[http://bada.com/ Bada]/[https://www.tizen.org/ Tizen]||[[Compiling ScummVM/Bada/Tizen|Bada/Tizen]] instructions<br />
|-<br />
|[http://www.raspberrypi.org/ RaspberryPi]]||[[Compiling ScummVM/RPI|Raspberry Pi]] instructions<br />
|}<br />
<br />
If you have instructions for compiling a port of ScummVM that is not mentioned here, feel free to contact us!</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM&diff=21615Compiling ScummVM2015-03-21T19:02:33Z<p>Vanfanel: /* Compiling ScummVM */</p>
<hr />
<div>{{Languages}}<br />
=== Compiling ScummVM ===<br />
<br />
ScummVM is written in C++ and has been ported to several different [[Platforms]]. Compilation of ScummVM is a bit different for each platform, so instructions have been included for the official platforms that ScummVM can be compiled for.<br />
<br />
{| border="1" cellpadding="2"<br />
|- style="background:silver"<br />
|Platform||Compiling instructions<br />
|-<br />
|[http://www.microsoft.com Windows] || [[Compiling ScummVM/Visual Studio|Visual Studio (MSVC)]], [[Compiling_ScummVM/MinGW|MinGW]] and [[Compiling ScummVM/DevCPP|Dev-C++]] instructions<br />
|-<br />
|[http://www.linux.org Linux] || [[Compiling ScummVM/GCC|GCC]]<br />
|-<br />
|[http://os4.hyperion-entertainment.biz/ AmigaOS4] || [[Compiling ScummVM/AmigaOS4|AmigaOS4]]<br />
|-<br />
|[http://www.microsoft.com/windowsmobile/ Windows CE/Mobile] || [[Compiling_ScummVM/Windows_CE|Windows CE]] instructions<br />
|-<br />
|[http://www.sega.jp/dc/ Sega Dreamcast] || [[Compiling ScummVM/Dreamcast|Dreamcast]] instructions<br />
|-<br />
|[http://www.us.playstation.com/PSP Sony PlayStation Portable]||[[Compiling ScummVM/PlayStation Portable|PlayStation Portable]] instructions<br />
|-<br />
|[http://www.us.playstation.com/PS2 Sony PlayStation 2]||[[Compiling ScummVM/PlayStation 2|PlayStation 2]] instructions<br />
|-<br />
|[http://us.playstation.com/ps3/ Sony PlayStation 3]||[[PlayStation_3#Building_from_source|PlayStation 3]] instructions<br />
|-<br />
|[http://www.apple.com/macosx/ Mac OS X]||[[Compiling ScummVM/Mac OS X|Mac OS X]] instructions (see also [[Compiling ScummVM/Mac OS X Crosscompiling|Mac OS X Crosscompiling]] and [[Compiling ScummVM/Mac OS X 10.2.8|Mac OS X 10.2.8]] instructions)<br />
|-<br />
|[http://www.apple.com/iphone/ Apple iPhone]||[[Compiling ScummVM/iPhone|iPhone]] instructions<br />
|-<br />
|[http://www.nintendo.com/ds Nintendo DS]||[[Compiling ScummVM/Nintendo DS|Nintendo DS]] instructions<br />
|-<br />
|[http://www.symbian.com/ Symbian]||[[Compiling ScummVM/Symbian|Symbian]] instructions<br />
|-<br />
|[http://wiki.sparemint.org/index.php/FreeMiNT Atari/FreeMiNT]||[[Compiling ScummVM/Atari/FreeMiNT|Atari/FreeMiNT]]<br />
|-<br />
|[http://en.wikipedia.org/wiki/BeOS BeOS]/[http://www.zeta-os.com/ ZETA]/[http://www.haiku-os.org/ Haiku]||[[Compiling ScummVM/BeOS/ZETA/Haiku|BeOS/ZETA/Haiku]] instructions<br />
|-<br />
|[http://www.nintendo.com/wii Nintendo Wii and Gamecube]||[[Compiling ScummVM/Wii|Wii and Gamecube]] instructions<br />
|-<br />
|[http://www.android.com/ Google Android]||[[Compiling ScummVM/Android|Android]] instructions<br />
|-<br />
|[https://developer.palm.com/ HP webOS]||[[Compiling ScummVM/WebOS|WebOS]] instructions<br />
|-<br />
|[http://www.maemo.org/ Maemo]||[[Compiling ScummVM/Maemo|Maemo]] instructions<br />
|-<br />
|[http://bada.com/ Bada]/[https://www.tizen.org/ Tizen]||[[Compiling ScummVM/Bada/Tizen|Bada/Tizen]] instructions<br />
|-<br />
|[http://www.raspberrypi.org/ RaspberryPi]]||[[Compiling ScummVM/RaspberryPi|RPI]] instructions<br />
|}<br />
<br />
If you have instructions for compiling a port of ScummVM that is not mentioned here, feel free to contact us!</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM&diff=21614Compiling ScummVM2015-03-21T19:01:05Z<p>Vanfanel: /* Compiling ScummVM */</p>
<hr />
<div>{{Languages}}<br />
=== Compiling ScummVM ===<br />
<br />
ScummVM is written in C++ and has been ported to several different [[Platforms]]. Compilation of ScummVM is a bit different for each platform, so instructions have been included for the official platforms that ScummVM can be compiled for.<br />
<br />
{| border="1" cellpadding="2"<br />
|- style="background:silver"<br />
|Platform||Compiling instructions<br />
|-<br />
|[http://www.microsoft.com Windows] || [[Compiling ScummVM/Visual Studio|Visual Studio (MSVC)]], [[Compiling_ScummVM/MinGW|MinGW]] and [[Compiling ScummVM/DevCPP|Dev-C++]] instructions<br />
|-<br />
|[http://www.linux.org Linux] || [[Compiling ScummVM/GCC|GCC]]<br />
|-<br />
|[http://os4.hyperion-entertainment.biz/ AmigaOS4] || [[Compiling ScummVM/AmigaOS4|AmigaOS4]]<br />
|-<br />
|[http://www.microsoft.com/windowsmobile/ Windows CE/Mobile] || [[Compiling_ScummVM/Windows_CE|Windows CE]] instructions<br />
|-<br />
|[http://www.sega.jp/dc/ Sega Dreamcast] || [[Compiling ScummVM/Dreamcast|Dreamcast]] instructions<br />
|-<br />
|[http://www.us.playstation.com/PSP Sony PlayStation Portable]||[[Compiling ScummVM/PlayStation Portable|PlayStation Portable]] instructions<br />
|-<br />
|[http://www.us.playstation.com/PS2 Sony PlayStation 2]||[[Compiling ScummVM/PlayStation 2|PlayStation 2]] instructions<br />
|-<br />
|[http://us.playstation.com/ps3/ Sony PlayStation 3]||[[PlayStation_3#Building_from_source|PlayStation 3]] instructions<br />
|-<br />
|[http://www.apple.com/macosx/ Mac OS X]||[[Compiling ScummVM/Mac OS X|Mac OS X]] instructions (see also [[Compiling ScummVM/Mac OS X Crosscompiling|Mac OS X Crosscompiling]] and [[Compiling ScummVM/Mac OS X 10.2.8|Mac OS X 10.2.8]] instructions)<br />
|-<br />
|[http://www.apple.com/iphone/ Apple iPhone]||[[Compiling ScummVM/iPhone|iPhone]] instructions<br />
|-<br />
|[http://www.nintendo.com/ds Nintendo DS]||[[Compiling ScummVM/Nintendo DS|Nintendo DS]] instructions<br />
|-<br />
|[http://www.symbian.com/ Symbian]||[[Compiling ScummVM/Symbian|Symbian]] instructions<br />
|-<br />
|[http://wiki.sparemint.org/index.php/FreeMiNT Atari/FreeMiNT]||[[Compiling ScummVM/Atari/FreeMiNT|Atari/FreeMiNT]]<br />
|-<br />
|[http://en.wikipedia.org/wiki/BeOS BeOS]/[http://www.zeta-os.com/ ZETA]/[http://www.haiku-os.org/ Haiku]||[[Compiling ScummVM/BeOS/ZETA/Haiku|BeOS/ZETA/Haiku]] instructions<br />
|-<br />
|[http://www.nintendo.com/wii Nintendo Wii and Gamecube]||[[Compiling ScummVM/Wii|Wii and Gamecube]] instructions<br />
|-<br />
|[http://www.android.com/ Google Android]||[[Compiling ScummVM/Android|Android]] instructions<br />
|-<br />
|[https://developer.palm.com/ HP webOS]||[[Compiling ScummVM/WebOS|WebOS]] instructions<br />
|-<br />
|[http://www.maemo.org/ Maemo]||[[Compiling ScummVM/Maemo|Maemo]] instructions<br />
|-<br />
|[http://bada.com/ Bada]/[https://www.tizen.org/ Tizen]||[[Compiling ScummVM/Bada/Tizen|Bada/Tizen]] instructions<br />
|-<br />
|[http://www.raspberrypi.org/ RaspberryPi]]||[[Compiling ScummVM/RaspberryPi|RaspberryPi]] instructions<br />
|}<br />
<br />
If you have instructions for compiling a port of ScummVM that is not mentioned here, feel free to contact us!</div>Vanfanelhttps://wiki.scummvm.org/index.php?title=Compiling_ScummVM/RPI&diff=21613Compiling ScummVM/RPI2015-03-21T18:57:48Z<p>Vanfanel: Created page with "== Cross-compiling ScummVM on for Raspberry Pi == == Installing the official Raspberry Pi cross-compiler on PC == We will clone the Raspberry Pi tools repository which includes..."</p>
<hr />
<div>== Cross-compiling ScummVM on for Raspberry Pi ==<br />
<br />
== Installing the official Raspberry Pi cross-compiler on PC ==<br />
<br />
We will clone the Raspberry Pi tools repository which includes the cross-compiler we need:<br />
<br />
git clone git://github.com/raspberrypi/tools.git<br />
<br />
It will get cloned to a directory called raspberrypi at your current location.<br />
<br />
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 raspberrrypi at my home directory, I would do:<br />
<br />
PATH=$PATH:/home/manuel/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin<br />
<br />
After adding the crosscompiler executables directory to the 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've the crosscompiler installed and accesible.<br />
<br />
== Installing the needed Raspberry Pi headers and libraries on PC ==<br />
<br />
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. <br />
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.<br />
<br />
So let's go with the headers and libs copy. I copied them to /home/manuel/rpi_root:<br />
<br />
cp -R <SD_mountpoint_directory>/usr /home/manuel/rpi_root<br />
cp -R <SD_mountpoint_directory>/lib /home/manuel/rpi_root<br />
cp -R <SD_mountpoint_directory>/opt /home/manuel/rpi_root<br />
<br />
== Configuring ScummVM ==<br />
<br />
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:<br />
<br />
RPI_ROOTDIR="/home/manuel/rpi_root" ./configure --backend=raspberrypi --host=raspberrypi --disable-debug --enable-release --enable-optimizations --disable-mt32emu --disable-flac \<br />
--disable-mad --disable-vorbis --disable-tremor \<br />
--disable-fluidsynth --disable-taskbar --disable-timidity --disable-alsa<br />
<br />
== Compiling ScummVM ==<br />
<br />
run "make clean" and then "make -j<n>", where n is the number of cores available on your compilation machine x2.<br />
<br />
== Installing ScummVM ==<br />
<br />
Simply copy over the resulting scummvm executable to your Raspberry Pi sd. A good idea is to create an scummvm folder in your /home/pi directory, and put the executable there along with the games you want to use with it.</div>Vanfanel