Compiling ScummVM/AmigaOS4
Jump to navigation
Jump to search
Compiling ScummVM for AmigaOS4
For building ScummVM on AmigaOS4, use the following build instructions:
Prerequisite
- Download and install the latestt AmigaOS4 SDK from Hyperion-Entertainment.
- Download and install SDL(1 or 2) (where SDL2 should always be preferred) SDK from GitHub.
- You may also need libogg, libvorbisfile, libvorbis, libFLAC, libmad, libtheoradec, libfaad(2), libmpeg2, liba52, libfreetype, libGL and/or libogles2 (and maybe more as more dependancies are added)
- Download them from OS4Depot.net.
Configuring
Run the configure script.
- type
sh ./configure --enable-plugins --disable-detection-full --enable-release
(Instead of
--enable-release
use
--enable-debug
to add debug flags.
--enable--plugins
is the command to build a shared objects version of ScummVM.
If you must (see below), use
--enable-static
to build the static version.)
for a list of configure options, additional features etc. (e.g. not yet enabled/unstable engines), use
sh ./configure --help
If no errors came up, you are ready to compile ScummvM.
Compiling
Note on static builds:
If you are trying to build ScummVM statically linked (all-in-one binary) your system memory will likely run out during the linking process.
The currently available AmigaOS4 NG systems are limited to 2 GB of RAM (where the limit actually stops at roughly 1550 MB) on the OS level (this may change in the future, but right now i would advise against a natively build static binary. (Cross-compiled static builds are still available throught the ScummVM buildbot (https://buildbot.scummvm.org/#/), albeit not with all available features).- type
gmake clean
in the directory ScummVM was configured and then
gmake amigaosdist
This will automatically install the ready binary with all needed dependancies into a subdirectory named "install/".
This directory can then be copied anywhere and used.
Installing
Copy (and rename, if needed) the final "install/" subdirectory wherever you want.
Running
Double-click the "ScummVM" icon to start the program (if no .ini settings file is availbale, an initial one with default settings will be created during the first run)