Skip to content

Compiling

Jump to bottom
chino edited this page Mar 20, 2013 · 6 revisions

Quick and Easy Dev Setup

You should read the rest of this page (particularly Compiling) but to get started quickly and easily you can follow this link:

quick-and-easy-dev-setup

Makefile / Compiler Switches

See the Makefile for more information.

Also see Preprocessor.

Compilers

Forsaken has been at one point or another compiled with:

  • mvsc 2007/8/12
  • winegcc
  • gcc
  • mingw
  • clang

The makefile supports 32bit and 64bit compiling.

forsaken-libs

Also check out the forsaken-libs repo which will help you compile all required libraries and setup your environment.

Safe Code

Add compile/runtime safety around array/pointer access even within forsaken memory space (unlike Valgrind).

It's also fast enough to play real games with it fully instrumenting your code...

Checkout http://safecode.cs.illinois.edu for more information.

Game Folder

After compiling, when you run the projectx binary it needs to know where to find your game folder that has all your assets and local configs.

The basic expected layout is:

├── configs          - local game configs
├── data             - [forsaken-data](https://github.com/ForsakenX/forsaken-data)
├── logs             - log folder
├── pilots           - pilot config
├── savegame         - save game files
├── scripts          - lua runtime scripts
├── OpenAL32.dll     - only required on win32 systems (or may be in system folders)
├── SDL.dll          - only required on win32 systems (or may be in system folders)

You have a few options:

  • Use -chdir cli flag (must be last option) to point to your existing forsaken install (or get it here: quick start page).

  • Use this folder as your game folder (create above folders) and clone forsaken-data.

  • Combine both steps above to create a game folder somewhere else.

Also note that the lua runtime scripts folder above is part of this repository hence you may want to symlink this to your game folder if your actively developing it.

Some day we may add a range of proper cli options so you can specify the path to each of the above folders and default user configs to something like ~/.forsakenx and %USERPROFILE% on win32.

Clone this wiki locally