| | 1 | [[OutdatedPage]] |
| | 2 | 1. Get the ebuild: source:/trunk/scripts/gentoo#HEAD (download newest ebuild) |
| | 3 | 1. Change to root user |
| | 4 | {{{ |
| | 5 | wraith root # su - |
| | 6 | }}} |
| | 7 | 1. Copy the ebuild to /usr/portage/games-action/orxonox (and create new directory) |
| | 8 | 1. |
| | 9 | {{{ |
| | 10 | wraith root # cd /usr/portage/games/action/orxonox |
| | 11 | wraith root # ebuild orxonox-*.ebuild digest |
| | 12 | wraith root # emerge orxonox |
| | 13 | }}} |
| | 14 | |
| | 15 | From now on you should be able to play Orxonox, and if you have subversion installed and a login, you will also be able to develop. |
| | 16 | |
| | 17 | === Installing the Libraries === |
| | 18 | Install the following libraries: |
| | 19 | * SDL main, media-libs/libsdl, web: http://www.libsdl.org/ |
| | 20 | * SDL_image, media-libs/sdl-image, web: http://www.libsdl.org/SDL_image |
| | 21 | * SDL_(true type fonts), media-libs/sdl-ttf, web: http://www.libsdl.org/SDL_ttf |
| | 22 | * SDL_net, media-libs/sdl-net, web http://www.libsdl.org/SDL_net |
| | 23 | * Glew library |
| | 24 | * OpenAl library |
| | 25 | * libvorbis |
| | 26 | |
| | 27 | Here are the commands to enter: |
| | 28 | {{{ |
| | 29 | wraith root # emerge media-libs/libsdl |
| | 30 | ... |
| | 31 | wraith root # emerge media-libs/sdl-image |
| | 32 | ... |
| | 33 | wraith root # emerge media-libs/sdl-ttf |
| | 34 | ... |
| | 35 | wraith root # emerge media-libs/sdl-net |
| | 36 | ... |
| | 37 | wraith root # emerge glew |
| | 38 | ... |
| | 39 | wraith root # emerge openal |
| | 40 | ... |
| | 41 | wraith root # emerge libvorbis |
| | 42 | ... |
| | 43 | wraith root # emerge qt |
| | 44 | |
| | 45 | }}} |
| | 46 | |
| | 47 | Or one big one-liner: |
| | 48 | {{{ |
| | 49 | wraith root # emerge libsdl sdl-image sdl-ttf sdl-net glew openal libvorbis qt |
| | 50 | }}} |
| | 51 | |
| | 52 | ==== LUA Scripting language ==== |
| | 53 | Lua is used for scripting in Orxonox, and it will be pulled in while comfiguring. |
| | 54 | There is also the possibility to use system wide lua installation (aka. emerged package). At the time of this writing, Orxonox is only compatible with lua-5.0.x. Any other version might cause some undesired effects like not being able to compile. [12/2/2007] |
| | 55 | |
| | 56 | |
| | 57 | |
| | 58 | Gentoo is now ready to compile and then run Orxonox.[[br]] |
| | 59 | |
| | 60 | |
| | 61 | === Getting the Source Code === |
| | 62 | First of all you have to install subversion on your system: Make sure, that you have '''ssl''' included in your ''make.conf'' file:[[br]] |
| | 63 | '''/etc/make.conf''' |
| | 64 | {{{ |
| | 65 | ... |
| | 66 | USE="..., ssl, ..." |
| | 67 | ... |
| | 68 | }}} |
| | 69 | now emerge subversion |
| | 70 | {{{ |
| | 71 | wraith user # emerge subversion |
| | 72 | }}} |
| | 73 | Check out the source via anonymous subversion login. This will download the whole project to the directory orxonox-dir. |
| | 74 | {{{ |
| | 75 | wraith user # svn co http://svn.orxonox.net/orxonox orxonox-dir |
| | 76 | }}} |
| | 77 | 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: |
| | 78 | {{{ |
| | 79 | wraith user # svn co https://svn.orxonox.net/orxonox orxonox-dir |
| | 80 | }}} |
| | 81 | You will be asked for your username and password, that you got from us. |
| | 82 | |
| | 83 | |
| | 84 | === Compiling === |
| | 85 | Just change into the trunk directory, then execute configure and make.... |
| | 86 | {{{ |
| | 87 | wraith user # cd ./orxonox/trunk/ |
| | 88 | wraith user # ./autogen.sh |
| | 89 | wraith user # ./configure |
| | 90 | ... |
| | 91 | wraith user # make |
| | 92 | ... |
| | 93 | wraith user # cd src |
| | 94 | wraith user # ./orxonox |
| | 95 | }}} |
| | 96 | |
| | 97 | |
| | 98 | === Profiling === |
| | 99 | If you want to profile Orxonox (measure its performance) you will probably want to view the statistics in a special program like kprof. On Gentoo systems you can just emerge it: |
| | 100 | {{{ |
| | 101 | wraith root # emerge kprof |
| | 102 | }}} |
| | 103 | Orxonox runs much much slower with profiling enabled. |
| | 104 | {{{ |
| | 105 | wraith user # cd ./orxonox/trunk/ |
| | 106 | wraith user # ./configure --enable-profile |
| | 107 | ... |
| | 108 | wraith user # make |
| | 109 | ... |
| | 110 | wraith user # cd src |
| | 111 | wraith user # ./orxonox |
| | 112 | }}} |
| | 113 | Orxonox now runs very slow and writes its profiling stats to a file called gmon.out. Remember that _only_ the functionalities you use while profiling will be profiled (since the profile log is written while the program is been executed). [[br]] |
| | 114 | After you exit the Orxonox, you can parse the output file and then be able to open it in kprof: |
| | 115 | {{{ |
| | 116 | wraith user # gprof -b ./orxonox > text.out |
| | 117 | wraith user # kprof -f text.out |
| | 118 | }}} |
| | 119 | For more documentation see the [wiki:DevelopmentResources development resources]. |