_______________________
       /\                      \
       \_|         Arx         |
         |      Libertatis     |
         |   __________________|__
          \_/____________________/

Cross-platform port of Arx Fatalis

Arx Libertatis is based on the publicly released Arx Fatalis source code. The source code is availbale under the GPLv3+ license with some additonal terms - see the COPYING and LICENSE files for details.

Contact

Website: http://arx-libertatis.org/

Bug Tracker: https://bugs.arx-libertatis.org/

IRC: #arxfatalis on irc.freenode.net

Wiki: http://wiki.arx-libertatis.org/

Reddit: http://www.reddit.com/r/ArxFatalis/

Dependencies

• CMake 2.8+ (compile-time only, 2.8.5+ under Windows)
• zlib
• Boost 1.48+ (headers only)
• GLM 0.9.2.7+
• FreeType 2.3.0+
• OpenAL 1.1+ (OpenAL Soft strongly recommended!)

Systems without Win32 or POSIX filesystem support will also the filesystem and system libraries from Boost.

Renderer

There is currently a single rendering backend for OpenGL:

• SDL 1.2.10+ or 2.0.0+
• OpenGL 1.5+ (OpenGL 2.1 or newer is recommended)
• GLEW 1.5.2+

Crash Reporter

Arx Libertatis comes with an optional gui crash reporter which has additional dependencies:

• Qt 4.7+ or 5 (QtCore, QtGui, QtWidgets^1 and QtNetwork libraries)
• GDB (Linux-only, optional, run-time only)
• DbgHelp (Windows-only)

1. Qt 5 only

While the crash reporter can be run without GDB, it's main usefulness comes from generating and submitting detailed back-traces in the event of a crash. On non-window systems we use GDB, the GNU Debugger, to accomplish that. If you want to help out the arx project, please install GDB before running arx. GDB is however purely a run-time dependency and is not needed when building the crash reporter.

Compile and install

For Linux run:

$ mkdir build && cd build && cmake ..
$ make

To install the binaries system-wide, run as root:

# make install

Alternatively you can run the game by specifying the full path to the arx binary in the build directory.

The wiki has more detailed instructions on compiling under Linux.

Getting all the dependencies set up for Windows is more tricky. Pre-build dependencies are available in the ArxWindows repository and instructions on how to use them are available on the wiki.

Build options:

• BUILD_TOOLS (default=ON): Build tools
• BUILD_CRASHREPORTER (default=ON): Build the Qt crash reporter gui (default OFF for Mac)
• UNITY_BUILD (default=OFF): Unity build (faster build, better optimizations but no incremental build)
• CMAKE_BUILD_TYPE (default=Release): Set to Debug for debug binaries
• DEBUG (default=OFF^1): Enable debug output and runtime checks
• DEBUG_EXTRA (default=OFF): Expensive debug options

1. Enabled automatically if CMAKE_BUILD_TYPE is set to Debug.

Install options:

• CMAKE_INSTALL_PREFIX (default: /usr/local on UNIX and C:/Program Files on Windows): Where to install Arx Libertatis

Set options by passing -D<option>=<value> to cmake.

Backends that are not available are disabled by default. The cmake run should display a summary of the enabled backends at the end.

Advanced options not listed here are documented in OPTIONS.md.

Data file, config and savegame locations

You will need to get either the full game or demo data of Arx Fatalis. To install the data files run

$ arx-install-data

Where arx will look for data files and write config and save files depends on the operating system and environment - the wiki has a page detailing the full data directory detection algorithm.

The game will try to rename all used files in the user directory (but not the data directory) to lowercase on the first run. System-wide installations with case-sensitive filesystems always need to manually rename the files to lowercase - this is done automatically by the arx-install-data script.

To print all directories searched by arx, run

$ arx --list-dirs

By default, user, config and data files will be loaded from and saved to standard system locations depending on the OS:

Windows:

• user and config dir:
  XP: %USERPROFILE%\My Documents\My Games\Arx Libertatis
  Vista and up: %USERPROFILE%\Saved Games\Arx Libertatis
• data dir: location stored in HKCU\Software\ArxLibertatis\DataDir or HKLM\Software\ArxLibertatis\DataDir registry keys

Mac OS X:

• user and config dir: ~/Library/Application Support/ArxLibertatis/
• data dir: /Applications/ArxLibertatis/

Linux and others:

• user dir: ~/.local/share/arx/
• config dir: ~/.config/arx/
• data dir: /usr/share/games/arx/, /usr/local/share/games/arx/ and more

Arx will also try to load data files from the directory containing the game executable.

To use the current working directory for user, config and data files (e.g. for a portable install) run the game as

$ arx --no-data-dir --user-dir=. --config-dir=.

Run

Provided the data files are installed at the correct location, you can simply play the game using the installed shortcut or by running

$ arx

See the arx --help and man arx output for more details.

Tools

• arxunpak <pakfile> [<pakfile>...]
  Extracts the .pak files containing the game assets.

• arxsavetool <command> <savefile> [<options>...] - commands are:

  • extract <savefile>
    Extract the contents of the given savefile to the current directory
  • add <savefile> [<files>...]
    Add files to a savefile, create it if needed
  • fix <savefile>
    Fix savegame issues created by previous builds of Arx Libertatis
  • view <savefile> [<ident>]
    Print savegame information - leave out <ident> to list root files

Scripts

The arx-install-data script can extract and install the game data under Linux and FreeBSD from the CD, demo, GOG.com installer or any Arx Fatalis install (such as on Steam) - simply run it and follow the GUI dialogs. Also see the wiki page on installing the game data under Linux.

Or, if you prefer a command-line interface, run it as

$ arx-install-data --cli

More options and required tools (depending on the source file) are documented in the help output:

$ arx-install-data --help

Developer information

To build developer documentation (doxygen), run this from the build directory:

$ make doc

To check for coding style problems, run the following: (requires python)

$ make style