TracNav(TracNav/TOC_install)?

Debian GNU/Linux

Last checked: 13. Feb. 2008 by Nowic? on Debian Lenny (Testing)

Unfortunately here is not yet a Debian package available for Orxonox. We're eager to release one, though.

Dependencies

To install all tools and libraries use the following command

  $ sudo aptitude install build-essential cmake libogre-dev libois-dev libboost-thread-dev libopenal-dev libalut-dev libenet-dev libfreeimage-dev libzzip-dev liblua5.1-0-dev tcl8.4-dev

Get the source

Check out the source via anonymous subversion login. This will download the whole project to the directory orxonox-dir.

$ svn co http://svn.orxonox.net/orxonox/trunk orxonox-trunk

You won't be able to commit your own code (check in) with the anonymous subversion repository. You have to ask us for a username/password combination. If you already have an account, check it out like this:

$ svn co https://svn.orxonox.net/orxonox/trunk orxonox-trunk

You will be asked for your username and password, that you got from us.

We have a seperate data repository. Download it via SVN as well:

$ svn co http://svn.orxonox.net/data/Media Media

Compile

$ cd orxonox-trunk
$ cmake .
...
$ make
...
$ ./run

Possible Bugs

The sound is strange

Install and run it with the Alsa-OSS-wrapper

$ sudo aptitude install alsa-oss
...
$ aoss ./run

---

This is an outdated page! This page is very old and the content is not up to date. Not everything (if any) which is written here will be in the final game!

Debian Sarge

Orxonox does not run on the official version of Debian Sarge because libqt4 is missing. Maybe using a backport of QT4 from ​http://backports.org/ could solve this problem (this has not yet been tested).

Debian Etch

Installing Orxonox on Debian Etch 4.0 works fine. Installing on Debian Testing (Lenny) and Debian SID (aka Unstable Debian) should work too (this has not yet been tested).

Installing the Libraries

wraith root # apt-get install libsdl1.2-dev libsdl-image1.2-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libqt4-dev libglut3-dev libglew-dev libopenal-dev libvorbis-dev libavformat-dev libcurl3-dev liblualib50-dev 
...

Users of the proprietary Nvidia driver need additional the nvidia opengl files:

wraith root # apt-get install nvidia-glx-dev

Installing Developer Tools

wraith root # apt-get install subversion automake1.9 g++

Getting the Source Code

Check out the source via anonymous subversion login. This will download the whole project to the directory orxonox-dir.

wraith user $ svn co http://svn.orxonox.net/orxonox/trunk orxonox-dir/trunk
wraith user $ svn co http://svn.orxonox.net/data/trunk orxonox-dir/data/trunk 

You won't be able to commit your own code (check in) with the anonymous subversion repository. You have to ask us for a username/password combination. If you already have an account, check it out like this:

wraith user $ svn co https://svn.orxonox.net/orxonox/trunk orxonox-dir/trunk
wraith user $ svn co https://svn.orxonox.net/data/trunk orxonox-dir/data/trunk

You will be asked for your username and password, that you got from us.

Compiling

Just change into the trunk directory, then execute configure and make….

wraith user $ cd ./orxonox/trunk/
wraith user $ ./autogen.sh
wraith user $ ./configure
...
wraith user $ make

Playing

wraith user $ cd ./orxonox/trunk/src
wraith user $ ./orxonox

Select the data file orxonox/data/trunk/data.oxd in the menu and play!

Profiling

If you want to profile Orxonox (measure its performance) you will probably want to view the statistics in a special program like kprof.

wraith root # apt-get install kprof

A word of warning: Orxonox runs much much slower with profiling enabled.

wraith user # cd ./orxonox/trunk/
wraith user # ./configure --enable-profile
...
wraith user # make
...
wraith user # cd src
wraith user # ./orxonox

Orxonox now runs very slowly and writes its profiling statistics to a file called gmon.out. Remember that _only_ the Orxonox functionalities you use while profiling will be profiled (since the profile log is written while the program is been executed).
After you exit Orxonox, you can parse the output file and then open it in kprof:

wraith user # gprof -b ./orxonox > text.out
wraith user # kprof -f text.out

For more documentation see the development resources.