Version 6 (modified by bensch, 19 years ago) (diff) |
---|
Get it Running
Debian Linux
Installing the Libraries
Install the following libraries:
- SDL main library, libsdl1.2-dev, web: link
- SDL image library, libsdl-image1.2-dev, web: link
- SDL true type fonts, libsdl-ttf2.0-dev, web: link
- SDL mixer, libsdl-mixer1.2-dev, web: link
You can also get these libraries from Debian packages: (Note: "libsdl-ttf2.0-dev" is only available for Debian "Sarge" (testing) and Debian SID (unstable)!)
wraith root # apt-get install libsdl1.2-dev libsdl-image1.2-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev ...
Getting the Source
First you will have to install the subversion program, make sure, that the ssl support is enabled
wraith root # apt-get install subversion
Check out the source via svn anonymous, this will download the hole project to the directory orxonox-dir
wraith user # svn co http://svn.orxonox.net/orxonox orxonox-dir
You won't be able to commit (check in) anything with the anonymous repository. You have to ask us for user/pass combination. If you have already an account check it out like this:
wraith user # svn co https://svn.orxonox.net/orxonox orxonox-dir
You will be asked for user name and password, that you have from us.
Compiling
Just change into the trunk directory, execute configure and make….
wraith user # cd ./orxonox/trunk/ wraith user # ./autogen.sh wraith user # ./configure ... wraith user # make ... wraith user # cd src wraith user # ./orxonox
Profiling
If you want to profile (performance measureing) orxonox you will probably want to view the statistics in a special program like kprof. On Gentoo systems you can just emerge it:
wraith root # apt-get install kprof
Orxonox runs much much slower with profiling enabled, so don't be embarassed!
wraith user # cd ./orxonox/trunk/ wraith user # ./configure --enable-profile ... wraith user # make ... wraith user # cd src wraith user # ./orxonox
Ok. Orxonox runs now (very slow) and writes its profiling stats to a file called gmon.out. Remember that _only_ those functinalities, that you are using while running the program will be profiled (since the profile log is written while the program is been executed).
After you exit the application, you will have to parse the output file and then you are able to open it in kprof application:
wraith user # gprof -b ./orxonox > text.out wraith user # kprof -f text.out
For more documentation see the DevelopmentResources.