Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Changeset 1796 in orxonox.OLD for orxonox/trunk/documentation/README


Ignore:
Timestamp:
Apr 12, 2004, 3:56:37 PM (21 years ago)
Author:
patrick
Message:

M documentation/README

File:
1 edited

Legend:

Unmodified
Added
Removed
  • orxonox/trunk/documentation/README

    r1795 r1796  
    4040To start programming on orxonox you first have to download the
    4141newest svn tree of orxonox. You can do this by enterning following
    42 lines in the linux console (ensure svn to be installed):
     42lines in the linux console (ensure svn to be installed with ssl
     43support enabled):
    4344
    4445svn co https://open.datacore.ch/pw/orxonox orxonox
    4546
    46 now have fun!
    47 PS: If you haven't got ssl support in you svn tool, recompile it
     47If you haven't got ssl support in you svn tool, recompile it
    4848./configure --with-ssl
    4949make
     
    6161
    6262
     63Howto SVN:
     64----------
     65For a more complete guide about this topic read the documentation
     66avaiable at subversion.tigris.org.
    6367
     68SVN (=subversion) is a version control program similar to CVS but
     69newer. This program enables us to work all at the same program at
     70the same time - tricky.
    6471
     72subversion checkout https://open.datacore.ch/pw/orxonox orxonox
     73same as: subversion co https://open.datacore....
     74
     75this makes a directory orxonox at your current place in and gets
     76the hole brand new source code from the server.
     77
     78now you can work. Remember to use 'svn copy instead of 'cp',
     79'svn mv' instead of 'mv', 'svn rm' instead of 'rm'... - you got it
     80I think.
     81After you have made your changes to the files enter
     82svn status
     83or with more details: svn status -vv
     84which will show you the changes you did locally on your computer.
     85svn diff
     86is similar but shows you all the changes in detail.
     87
     88svn diff > patchfile
     89the patchfile you can use later in conjunction with the patch program.
     90You could, for example, email this patchfile to another developer for
     91review or testing prior to commit.
     92
     93To add a new file type
     94svn add <filename>
     95and to publish all your changes type
     96svn commit
     97which will put all your changes to the orxonox server.
     98
     99If you accidently make a change you like to revert, you just can do this
     100by typing:
     101svn revert <filename>
     102
Note: See TracChangeset for help on using the changeset viewer.