| 1 | [[OutdatedPage]] |
| 2 | |
| 3 | === Debian Sarge === |
| 4 | 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). |
| 5 | |
| 6 | === Debian Etch === |
| 7 | 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). |
| 8 | |
| 9 | === Installing the Libraries === |
| 10 | |
| 11 | {{{ |
| 12 | 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 |
| 13 | ... |
| 14 | }}} |
| 15 | |
| 16 | Users of the proprietary Nvidia driver need additional the nvidia opengl files: |
| 17 | {{{ |
| 18 | wraith root # apt-get install nvidia-glx-dev |
| 19 | }}} |
| 20 | === Installing Developer Tools === |
| 21 | |
| 22 | {{{ |
| 23 | wraith root # apt-get install subversion automake1.9 g++ |
| 24 | }}} |
| 25 | |
| 26 | === Getting the Source Code === |
| 27 | |
| 28 | Check out the source via anonymous subversion login. This will download the whole project to the directory orxonox-dir. |
| 29 | {{{ |
| 30 | wraith user $ svn co http://svn.orxonox.net/orxonox/trunk orxonox-dir/trunk |
| 31 | wraith user $ svn co http://svn.orxonox.net/data/trunk orxonox-dir/data/trunk |
| 32 | }}} |
| 33 | 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: |
| 34 | {{{ |
| 35 | wraith user $ svn co https://svn.orxonox.net/orxonox/trunk orxonox-dir/trunk |
| 36 | wraith user $ svn co https://svn.orxonox.net/data/trunk orxonox-dir/data/trunk |
| 37 | }}} |
| 38 | You will be asked for your username and password, that you got from us. |
| 39 | |
| 40 | |
| 41 | === Compiling === |
| 42 | Just change into the trunk directory, then execute configure and make.... |
| 43 | {{{ |
| 44 | wraith user $ cd ./orxonox/trunk/ |
| 45 | wraith user $ ./autogen.sh |
| 46 | wraith user $ ./configure |
| 47 | ... |
| 48 | wraith user $ make |
| 49 | }}} |
| 50 | |
| 51 | === Playing === |
| 52 | {{{ |
| 53 | wraith user $ cd ./orxonox/trunk/src |
| 54 | wraith user $ ./orxonox |
| 55 | }}} |
| 56 | Select the data file orxonox/data/trunk/data.oxd in the menu and play! |
| 57 | |
| 58 | === Profiling === |
| 59 | If you want to profile Orxonox (measure its performance) you will probably want to view the statistics in a special program like kprof. |
| 60 | {{{ |
| 61 | wraith root # apt-get install kprof |
| 62 | }}} |
| 63 | A word of warning: Orxonox runs much much slower with profiling enabled. |
| 64 | {{{ |
| 65 | wraith user # cd ./orxonox/trunk/ |
| 66 | wraith user # ./configure --enable-profile |
| 67 | ... |
| 68 | wraith user # make |
| 69 | ... |
| 70 | wraith user # cd src |
| 71 | wraith user # ./orxonox |
| 72 | }}} |
| 73 | 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). [[br]] |
| 74 | After you exit Orxonox, you can parse the output file and then open it in kprof: |
| 75 | {{{ |
| 76 | wraith user # gprof -b ./orxonox > text.out |
| 77 | wraith user # kprof -f text.out |
| 78 | }}} |
| 79 | For more documentation see the [wiki:DevelopmentResources development resources]. |