50 | | |
51 | | ----- |
52 | | |
53 | | [[OutdatedPage]] |
54 | | |
55 | | === Debian Sarge === |
56 | | 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). |
57 | | |
58 | | === Debian Etch === |
59 | | 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). |
60 | | |
61 | | === Installing the Libraries === |
62 | | |
63 | | {{{ |
64 | | 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 |
65 | | ... |
66 | | }}} |
67 | | |
68 | | Users of the proprietary Nvidia driver need additional the nvidia opengl files: |
69 | | {{{ |
70 | | wraith root # apt-get install nvidia-glx-dev |
71 | | }}} |
72 | | === Installing Developer Tools === |
73 | | |
74 | | {{{ |
75 | | wraith root # apt-get install subversion automake1.9 g++ |
76 | | }}} |
77 | | |
78 | | === Getting the Source Code === |
79 | | |
80 | | Check out the source via anonymous subversion login. This will download the whole project to the directory orxonox-dir. |
81 | | {{{ |
82 | | wraith user $ svn co http://svn.orxonox.net/orxonox/trunk orxonox-dir/trunk |
83 | | wraith user $ svn co http://svn.orxonox.net/data/trunk orxonox-dir/data/trunk |
84 | | }}} |
85 | | 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: |
86 | | {{{ |
87 | | wraith user $ svn co https://svn.orxonox.net/orxonox/trunk orxonox-dir/trunk |
88 | | wraith user $ svn co https://svn.orxonox.net/data/trunk orxonox-dir/data/trunk |
89 | | }}} |
90 | | You will be asked for your username and password, that you got from us. |
91 | | |
92 | | |
93 | | === Compiling === |
94 | | Just change into the trunk directory, then execute configure and make.... |
95 | | {{{ |
96 | | wraith user $ cd ./orxonox/trunk/ |
97 | | wraith user $ ./autogen.sh |
98 | | wraith user $ ./configure |
99 | | ... |
100 | | wraith user $ make |
101 | | }}} |
102 | | |
103 | | === Playing === |
104 | | {{{ |
105 | | wraith user $ cd ./orxonox/trunk/src |
106 | | wraith user $ ./orxonox |
107 | | }}} |
108 | | Select the data file orxonox/data/trunk/data.oxd in the menu and play! |
109 | | |
110 | | === Profiling === |
111 | | If you want to profile Orxonox (measure its performance) you will probably want to view the statistics in a special program like kprof. |
112 | | {{{ |
113 | | wraith root # apt-get install kprof |
114 | | }}} |
115 | | A word of warning: Orxonox runs much much slower with profiling enabled. |
116 | | {{{ |
117 | | wraith user # cd ./orxonox/trunk/ |
118 | | wraith user # ./configure --enable-profile |
119 | | ... |
120 | | wraith user # make |
121 | | ... |
122 | | wraith user # cd src |
123 | | wraith user # ./orxonox |
124 | | }}} |
125 | | 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]] |
126 | | After you exit Orxonox, you can parse the output file and then open it in kprof: |
127 | | {{{ |
128 | | wraith user # gprof -b ./orxonox > text.out |
129 | | wraith user # kprof -f text.out |
130 | | }}} |
131 | | For more documentation see the [wiki:DevelopmentResources development resources]. |