|
UsingGit
Howto use the git repos of naev.
Featured IntroductionAfter version 0.3.6 NAEV changed VCS from mercurial to git for size among other reasons. This intends to be a brief guide on how to use git. Getting GitLinuxJust use your package manager to get it. WindowsRead this Windows Git Guide. Mac OS XYou might want to take a look at this Mac OS X git project. Using GitChecking outYou first do a checkout to get the repository. This should only be run once. It might take a while since NAEV is quite big currently. git clone git://github.com/bobbens/naev.git UpdatingIt is a good idea to update NAEV as often as possible. It is a developer goal to try to keep HEAD (latest version) always workable and this will help with bug reports. git pull Pulling branchesTo get an official branch you can do the following: # Pull the new branch called 'ewarfare' creating it locally git checkout -b ewarfare origin/ewarfare Then you can change between them and pull to update them whenever. Changing branchesGit work is usually done with branches. "master" is the one with all the bleeding edge changes while all releases past 0.3.8 will have their own. You can switch between them with stuff like: # Change to 0.3.9 branch git checkout NAEV-0.3.9 # Change back to bleeding edge master git checkout master This way you can try whatever version you want. CompilingNow create the configuration scripts with: ./autogen.sh Now you get to configure NAEV. Usually the defaults should be more then enough so run: ./configure And proceed to compile with: make If all went well you should see something like: $ make Making all in lib Making all in csparse CC cs_add.o CC cs_amd.o ... CC naev Making all in utils Making all in pack CC main.o CC md5.o CC pack.o CC pack $ Indicating the binary was built. Now you can run naev with: ./naev Enjoy! | |
http://forum.naev.org/viewtopic.php?f=10&t=93 is useful
For building on ubuntu; you'll need libsdl-dev