Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Changes between Version 37 and Version 38 of dev/Primer


Ignore:
Timestamp:
Apr 15, 2017, 1:00:44 PM (7 years ago)
Author:
landauf
Comment:

fixed links

Legend:

Unmodified
Added
Removed
Modified

  • dev/Primer

    v37 v38  
    2727Orxonox is programmed by many programmers at the same time. To synchronize the work and to make it available for all, we've got a central subversion server (subversion is a versioning system; the newer form of cvs). Most Linuxes already have svn (subversion) in their software repository (gentoo: portage tree, debian: apt-system), for Windows you need to install tortoise svn, which you can get here: http://tortoisesvn.tigris.org/ [[br]]
    2828If you want to read more about this topic, go to:
    29  * A [wiki:SVN list of SVN commands] written by Nico.
     29 * A [wiki:code/tools/SVN list of SVN commands] written by Nico.
    3030 * [http://svnbook.red-bean.com/en/1.1/index.html the official subversion guide, written very funnily]
    3131 * [http://www.onlamp.com/pub/a/onlamp/2002/10/31/subversion.html a shorter version]
    … …  
    4141
    4242== 6. Compiling and Running ==
    43 To get Orxonox running on your system, first read [wiki:Running how to get Orxonox running].
     43To get Orxonox running on your system, first read [wiki:download#Guides how to get Orxonox running].
    4444
    4545
    … …  
    5656
    5757== 8. Understanding Orxonox ==
    58 It definitely takes some time to understand the Orxonox source code. The best way to get your questions answered is to post them on the development-mailing list. Even better is to just go to the developers and ask specific questions. Once you know where to find which functions, you will want to read some more about special topics in the source files themselves: we use doxygen to comment the code, so you will find comments for every class/function. There are also [wiki:ModulesDescription module descriptions] which we are currently working on.
     58It definitely takes some time to understand the Orxonox source code. The best way to get your questions answered is to post them on the development-mailing list. Even better is to just go to the developers and ask specific questions. Once you know where to find which functions, you will want to read some more about special topics in the source files themselves: we use doxygen to comment the code, so you will find comments for every class/function. There are also [wiki:code/doc/ModulesDescription module descriptions] which we are currently working on.