Download

This article describes all aspects of downloading the latest version of PARPG and how to get it running. All of the following steps are mandatory to get PARPG running on your system, therefore none of them can be skipped.

Installing Python
As PARPG is written in Python, you'll need a Python interpreter installed to run the game. For Linux make sure that you install the latest release of the Python 2.5.x branch. Python <= 2.4 and >= 2.6 (including Py3k) will NOT work. For Win32 we strongly suggest to use the Active Python distribution as it's tested and proven to work with PARPG.

Getting the game engine
PARPG is based on the open source game engine FIFE. In the current stage of development we're using the latest SVN snapshot of FIFE for PARPG. You'll need a Subversion client to get your hands on the latest version of the engine. For Win32 users who haven't got an SVN client installed yet, we strongly recommend to check out TortoiseSVN.

Once you got your SVN client installed create a new folder for the game engine (called  from now on) and CD into it. Download the latest FIFE version by checking out the content of http://svn9.cvsdude.com/fife/engine/trunk/ into .

Getting PARPG
Now we'll grab the PARPG specific code and assets from their Subversion repository:
 * 1) CD into /clients/ and create a folder there.
 * 2) Check out the latest version from http://parpg-svn.cvsdude.com/parpg/trunk/game/ into /clients/.

Paths are hardcoded at the moment so you'll need to follow this guide and utilize the folder structure mentioned above. We can reorganize the structure later but for the ease of getting started, we'll work with this structure for now.

Linux

 * 1) Install the dependencies listed here: http://wiki.fifengine.de/Build_dependencies.
 * 2) CD into /build/ and run: scons ext=1 && scons.

Win32

 * 1) Get the latest version of FIFE compile SDK. The compile SDK is a complete package to build FIFE from source on Win32 systems. It contains needed build tools (mingw, scons, swig), all dependencies as precompiled static and dynamic libraries and their corresponding headers. You can grab the latest version here: http://downloads.sourceforge.net/fife/FIFE_2009.0_win32_SDK.7z.
 * 2) Unpack the compile SDK with a tool of your choice that supports the 7zip archive format to \build\win32.
 * 3) Optional step: CD into \build\win32\ and run update_project_files.bat. This step is just needed if you plan to build the engine with a different compiler than mingw.
 * 4) CD into \build\win32\build_environments\scons\ and run logbuild_engine.bat. FIFE will now get built using the mingw compiler that comes with the compile SDK. Other compilers and IDEs are supported as well (Code::Blocks, MSVC2005, MSVC2008) but the build process for them is not explained in the detail here. If you would like to build FIFE with a different compiler, check out the build guides at the FIFE wiki: http://wiki.fifengine.de/Guides_%26_tutorials#Win32.
 * 5) Wait until the console window that has popped up after you ran logbuild_engine.bat has closed again. FIFE should have been successfully compiled now. A detailed build report is written to \build\win32\build_environments\scons\engine_build_log.txt.

Starting PARPG
We're ready to start what will become PARPG now! Caution: the current version of PARPG is a simple copy of the FIFE techdemo Rio de hola. It will be used as starting point for the development of our game so we don't need to create everything from scratch.

Linux

 * 1) CD into /clients/ and run the Python script run.py.

Win32

 * 1) CD into \clients\ and run update_dlls_mingw.bat. It will copy the needed engine DLLs into the PARPG folder so you can start the game as next step. Note: this step is only needed when you're running PARPG for the first time or if you've updated the compile SDK or recently built FIFE with a different compiler.
 * 2) CD into \clients\ and run the Python script run.py by doubleclicking on it. It should be automatically associated with the Python interpreter of your system in case you're using ActivePython. If you're using a different Python distribution you might need to manually associate Python scripts with the interpreter on your system.