Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Changes between Version 8 and Version 9 of dev/LinuxDebian


Ignore:
Timestamp:
Oct 27, 2006, 1:50:47 PM (18 years ago)
Author:
simon
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • dev/LinuxDebian

    v8 v9  
    44
    55=== Debian Sarge ===
    6 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. (not tested yet)
     6Orxonox 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).
    77
    88=== Debian Etch (Testing) ===
    9 Installing Orxonox on Debian Etch (aka Testing). Installing on Debian SID (aka Unstable) should work too (not tested).
     9Installing Orxonox on Debian Etch (aka the Testing Debian). Installing on Debian SID (aka Unstable Debian) should work too (this has not yet been tested).
    1010
    1111=== Installing the Libraries ===
     
    1616}}}
    1717
    18 === Installing developer tools ===
     18=== Installing Developer Tools ===
    1919
    2020{{{
     
    2222}}}
    2323
    24 === Getting the Source & Data ===
     24=== Getting the Source Code ===
    2525
    26 Check out the source and data via svn anonymous, this will download the hole project to the directory orxonox-dir
     26Check out the source via anonymous subversion login. This will download the whole project to the directory orxonox-dir.
    2727{{{
    2828wraith user $ svn co http://svn.orxonox.net/orxonox orxonox-dir
    2929wraith user $ svn co http://svn.orxonox.net/data orxonox-dir/data
    3030}}}
    31 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:
     31You 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:
    3232{{{
    3333wraith user $ svn co https://svn.orxonox.net/orxonox orxonox-dir
    3434wraith user $ svn co https://svn.orxonox.net/data orxonox-dir/data
    3535}}}
    36 You will be asked for user name and password, that you have from us.
     36You will be asked for your username and password, that you got from us.
    3737
    3838
    3939=== Compiling ===
    40 Just change into the trunk directory, execute configure and make....
     40Just change into the trunk directory, then execute configure and make....
    4141{{{
    4242wraith user $ cd ./orxonox/trunk/
     
    5555
    5656=== Profiling ===
    57 If you want to profile (performance measureing) orxonox you will probably want to view the statistics in a special program like kprof.
     57If you want to profile Orxonox (measure its performance) you will probably want to view the statistics in a special program like kprof.
    5858{{{
    5959wraith root # apt-get install kprof
    6060}}}
    61 Orxonox runs much much slower with profiling enabled, so don't be embarassed!
     61A word of warning: Orxonox runs much much slower with profiling enabled.
    6262{{{
    6363wraith user # cd ./orxonox/trunk/
     
    6969wraith user # ./orxonox
    7070}}}
    71 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). [[br]]
    72 After you exit the application, you will have to parse the output file and then you are able to open it in kprof application:
     71Orxonox 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]]
     72After you exit Orxonox, you can parse the output file and then open it in kprof:
    7373{{{
    7474wraith user # gprof -b ./orxonox > text.out
    7575wraith user # kprof -f text.out
    7676}}}
    77 For more documentation see the DevelopmentResources.
     77For more documentation see the [wiki:DevelopmentResources development resources].