To build Antares from source, follow these instructions in a terminal window:
$ git clone https://github.com/arescentral/antares.git $ cd antares
Configure the project:
You may be missing some dependencies. If the configure script fails, then install them as instructed, and run ./configure again.
Optional: read more about ./configure.
Optional: read more about make.
$ make run
Run the tests:
$ make test
Optional: read more about make test.
(Mac only) For a release build, sign the binary:
$ make sign
(Linux only) Install the game:
$ sudo make install
This will install the game to /usr/local/games/antares, by default. You can choose a different location with ./configure.
Normally, it’s sufficient to run ./configure without any arguments. However, there are some options you can pass to build Antares in different ways:
By default, Antares will be configured in opt mode, meaning that it will try to make the resulting binary as fast as possible. For development, you may want to use dev mode, which will try to speed up the compilation process instead:
$ ./configure --mode=dev
If you expect to use lldb with the resulting binary, you may want to use dbg mode, which compiles the binary with debugging information:
$ ./configure --mode=dbg
If in doubt, use --mode=dev if you’re planning to do development work, and use the default if you just want a more recent version of the game.
On Linux, the game is installed to /usr/local/games/antares by default. The --prefix argument to ./configure changes this.
$ ./configure --prefix=/opt/antares
The make command (with no arguments) is a wrapper around ninja. You can also use ninja directly, which exposes additional options.
Keep building even after a failure:
$ build/lib/bin/ninja -C out/cur -k 0
Antares has an extensive suite of regression tests. These play through several different levels of the game to verify that the same behavior is observed for the same input.
If you’re running the tests frequently, running in smoke-test mode will speed up the tests:
$ make smoke-test
There are more options if you use the wrapped script directly:
$ make $ scripts/test.py --type=replay