1. Install gemrb
2. Install the game(s)
3. Configure gemrb
4. Test run

If you don't need or want the latest developments (available via SVN), just use the packages provided by your distributor. If they don't exist, check the next section and/or ask the distributor to make a package.

Make sure you have sdl, openal, python, zlib and g++ installed (with all their header/devel packages if they exist). If you'll be building from SVN, you also need all the autotools (autoconf, automake, libtool).

First you'll need to get the source. Either in the form of a release tarball or the latest source from SVN.

Download the source tarball from the project page.

Create a checkout of gemrb with:

svn co https://gemrb.svn.sourceforge.net/svnroot/gemrb/gemrb/trunk gemrb

1. cd gemrb
2. Run ./autogen.sh¹⁾, it will also run ./configure
3. make

1. Extract the tarball: tar xf gemrb*.tar.*
2. cd gemrb*
3. ./configure –prefix=$HOME/gemrb/²⁾
4. make

For a self-compiled gemrb, installation is not necessary. Merely run gemrb/plugins-prepare.sh and edit PluginsPath in the gemrb configuration files (p.e. gemrb.cfg).

Note that if you want to debug a not-installed gemrb with gdb, you need to start it like: gdb gemrb/.libs/lt-gemrb ³⁾.

Otherwise run the customary: make install

If you already have a game installed somewhere, even if it is on another OS, just make sure that that filesystem is mounted and point gemrb to the relevant directory (set GamePath in gemrb.cfg).

Just run the Setup.exe and follow through to the end.

See unshield. You can get it here.

1. Copy one of the GemRB.cfg samples and rename it to <game_name>.cfg . You can name configuration files arbitrarily, but this way makes the most sense if you'll be running multiple games.
2. Edit GemRB.cfg, mainly to set up the path to the game's data files. It is crucial you get this right. ⁴⁾

You will know gemrb is working perfectly once you can see the main game screen. If that doesn't happen, check the console for errors and fix the configuration file as needed. Usually some path is set wrong.

• Run the “gemrb” binary (you can specify the desired configuration like this: gemrb -c torment.cfg)
  • You can also link the gemrb binary to <game_name> and the start it with that link, so gemrb will automatically pick the right configuration file. That means there is no need to pass -c anymore (pst vs gemrb -c pst.cfg)