Difference between revisions of "Compiling ScummVM/RPI"

Line 61:

== Configuring ScummVM ==

Now we can configure ScummVM buildsystem so it knows what backend we ~~want~~ and where our Raspberry Pi local sysroot is located, containing the Raspberry Pi headers and libraries the cross-compiler and linker will need. In this example configuration, we disable debug symbols since it's intended for final users.

First, you should make sure have the latest version of the ScummVM code locally (using ''git clone'' or ''git pull'' appropriately).

Then, navigate inside your local ''scummvm'' source code folder.

Now we can configure ScummVM buildsystem so it knows what backend we target and where our Raspberry Pi ''local sysroot'' is located, containing the Raspberry Pi headers and libraries the cross-compiler and linker will need. In this example configuration, we disable debug symbols since it's intended for final users.

Difference between revisions of "Compiling ScummVM/RPI"

Navigation menu

Search

@@ Line 61: / Line 61: @@
 == Configuring ScummVM ==
-Now we can configure ScummVM buildsystem so it knows what backend we want and where our Raspberry Pi local sysroot is located, containing the Raspberry Pi headers and libraries the cross-compiler and linker will need. In this example configuration, we disable debug symbols since it's intended for final users.
+First, you should make sure have the latest version of the ScummVM code locally (using ''git clone'' or ''git pull'' appropriately).
+Then, navigate inside your local ''scummvm'' source code folder.
+Now we can configure ScummVM buildsystem so it knows what backend we target and where our Raspberry Pi ''local sysroot'' is located, containing the Raspberry Pi headers and libraries the cross-compiler and linker will need. In this example configuration, we disable debug symbols since it's intended for final users.
   <nowiki>