HowTo:Checkout SVN (Ubuntu Linux) - Revision history

Greendreamer: /* Downloading Vega Strike */ new repository localisation

2014-02-13T22:50:10Z

‎Downloading Vega Strike: new repository localisation

Rabiator at 16:28, 6 April 2013

2013-04-06T16:28:57Z

Rabiator at 16:23, 6 April 2013

2013-04-06T16:23:47Z

Iansterguy: /* Running Vega Strike */ Fixed goto to "go to"

2013-02-24T19:12:52Z

‎Running Vega Strike: Fixed goto to "go to"

Iansterguy: Divided the tutorials advanced instructions into individual advanced tutorials.

2013-02-24T19:10:30Z

Divided the tutorials advanced instructions into individual advanced tutorials.

Augie.ben.doggie: [vega-bot] [replace] 1 instances of 'http://vegastrike.sourceforge.net/forums' for 'http://forums.vega-strike.org'

2013-01-08T21:29:09Z

[vega-bot] [replace] 1 instances of 'http://vegastrike.sourceforge.net/forums' for 'http://forums.vega-strike.org'

Iansterguy: /* Building */ Removed a redundant "that"

2012-12-22T03:26:17Z

‎Building: Removed a redundant "that"

Iansterguy: /* Building/Compiling */ emphasized the difference between building and compiling

2012-12-22T03:15:39Z

‎Building/Compiling: emphasized the difference between building and compiling

Iansterguy: /* Building/Compiling */

2012-12-17T02:21:56Z

‎Building/Compiling

Tbeholder: 3g died after Lucid, while freeglut is old enough to cover old distros and "configure" script is OK with the replacement

2011-10-21T16:15:32Z

3g died after Lucid, while freeglut is old enough to cover old distros and "configure" script is OK with the replacement

@@ Line 26: / Line 26: @@
 Now we can start downloading the packages from the SVN repository. If you download them directly into your Vega Strike directory they will be just in the right place.
 * Download (check-out) the source code package vegastrike, and the content package data package.
-<pre>User@UserMachine:~/VegaStrike$ svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
+<pre>User@UserMachine:~/VegaStrike$ svn co https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike
 </pre>
 * After the first one finishes downloading (User@UserMachine:~/VegaStrike$ will reappear), insert the next. Be warned, you need a descent download speed to download the next package with this method.
-<pre>User@UserMachine:~/VegaStrike$ svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data</pre>
+<pre>User@UserMachine:~/VegaStrike$ svn co https://svn.code.sf.net/p/vegastrike/code/trunk/data</pre>
 This leaves you with two new directories inside your Vega Strike directory called as the packages are.
 == Building ==

@@ Line 41: / Line 41: @@
 ''Note that some recent distributions need python2.7-dev instead of python2.6-dev or python2.5-dev''
-Kubuntu 12.04 also does not install cmake and libxmu-dev by default. You can get those with
+Xubuntu 12.04 also does not install cmake and libxmu-dev by default. You can get those with
 <pre>sudo apt-get install cmake libxmu-dev </pre>

@@ Line 31: / Line 31: @@
 <pre>User@UserMachine:~/VegaStrike$ svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data</pre>
 This leaves you with two new directories inside your Vega Strike directory called as the packages are.
 == Building ==
@@ Line 46: / Line 40: @@
 </pre>
 ''Note that some recent distributions need python2.7-dev instead of python2.6-dev or python2.5-dev''
 === Compiling ===
-The compile procedure should look like the following listing. Remember, the configure part depends on above requirements. However, autoconf may not work. If so, just skip it.
+The compile procedure should look like the following listing. Remember, the configure part depends on above requirements. Autotools is no longer supported, so we need to follow the instructions for cmake instead:
-* Change directory.
+* Create a build directory somewhere outside of the source tree
-<pre>cd ./vegastrike</pre>
+<pre>User@UserMachine:~/VegaStrike$ mkdir build</pre>
-* Pre-Compile.
+* Run cmake <path to source tree> inside the build directory
-<pre>./bootstrap-sh</pre>
+<pre>User@UserMachine:~/VegaStrike$ cd build
-* Some configuration to be made.
+User@UserMachine:~/VegaStrike/build$ cmake ../vegastrike
-<pre>./configure --enable-release</pre>
+</pre>
-''"--enable-release"'' enables optimizations, you can add the opposite, ''"--enable-debug"'', if you feel like debugging (or getting stacktraces to aid debugging for developers - ie: to prepare a bug report). If you have the boost libraries installed in your system, you will likely want to use ''"--with-boost=system"'' too, to make VS use that one.
+* Compile. Make must be called from the build directory
-* Compile.
+<pre>User@UserMachine:~/VegaStrike/build$ make</pre>
 * Install.
 <pre>sudo make install # [AS ROOT]</pre>
-Note: you may not need to install, VS will run fine where it's built, provided its data is in ../data (relative to the source). Ie: the way it normally checks out of SVN.
+Note: you may not need to install, VS will run fine where it's built, provided its data is in ../data (relative to the source). Ie: the way it normally checks out of SVN. Also, install may be broken right now, "make install" did not work for me after the above steps :(
 == Running Vega Strike ==

@@ Line 64: / Line 64: @@
 == Running Vega Strike ==
-Just goto the directory ''vegastrike'' then run ./vssetup to setup the game options, then run ./vegastrike to start the game. If everything has gone well the main menu will appear where you can click on new campaign.
+Just go to the directory ''vegastrike'' then run ./vssetup to setup the game options, then run ./vegastrike to start the game. If everything has gone well the main menu will appear where you can click on new campaign.
 = Advanced Tutorials for less common or previously nessasary configurations and setups =

@@ Line 9: / Line 9: @@
 Note: This process was done in Ubuntu 8.10 (Intrepid), though it might work in Debian as well. Should be able to work in the Ubuntu derivatives, too.
-= Tutorial to Download, Compile, Setup and Run Vega Strike =
+= Basic Tutorial to Download, Compile, Setup and Run Vega Strike =
 == Downloading Vega Strike ==
 === Installing SVN ===
@@ Line 63: / Line 63: @@
 Note: you may not need to install, VS will run fine where it's built, provided its data is in ../data (relative to the source). Ie: the way it normally checks out of SVN.
-==== Configuring Installation ====
+== Running Vega Strike ==
 We need to make sure the data directory is *recognized*. For tutorial purposes, we will use the directory where we downloaded first in this tutorial.
 * Open text editor (Applications>Accessories>Text Editor), copy and paste the following code in text editor, change the USER in caps to the name of your user, and then paste in Terminal.
@@ Line 71: / Line 87: @@
 <pre>./configure --with-boost=1.35</pre>
-=== Make ===
+== Advanced Make ==
 The final step compiling is the command make.
 * For ''example'', to compile the mesher.
@@ Line 84: / Line 100: @@
 You might receive errors while doing any of the previous steps (make). If so, give privileges (sudo) before any of the commands.
-== Setup ==
+== Advanced Setup ==
 The next step is to setup the game. This is quite easy to do, so you are almost done.
@@ Line 99: / Line 115: @@
 *Optionally, you can right-click the vegastrike link and make yet another link. This link can be moved over to the desktop or menu.
-==== Optional High Quality Texture Files ====
+= Staying updated with the Development Version =
 As development progresses the repository changes. In order to update your working copy you need to do the following.
 * Open Terminal and change into the package's directory you want to update. In our tutorial example, all the packages were stored in a directory called ''VegaStrike''. Let's assume we want to update the ''data'' package.
@@ Line 128: / Line 133: @@
 * If something changed in the source code package vegastrike, you only need to repeat the building part of this tutorial. You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error.
-== Running Vega Strike ==
+= Troubleshooting =
-Very simple. Just goto the directory ''data'' and type ./vegastrike or simply double click the symbolic link. Same for ./vssetup.
+If you have trouble with compiz, try [http://forlong.blogage.de/entries/pages/Compiz-Switch this application] to temporarily disable compiz. Then, launch the game normally. The game will be much faster with compiz disabled, too.
-== Extra Info ==
+If you have trouble with starting the game perhaps try to work through the generic instructions in case somthing is significantly different between them. Else ask for help on the fourms in the section named [http://forums.vega-strike.org/viewforum.php?f=1&sid=63de74c4da0aad85e3417b72509a6e8c User Help].
 [[Category:fixme]]
 [[Category:HowTos|Checkout SVN (Ubuntu Linux)]]

@@ Line 6: / Line 6: @@
 ----
-This is a newb friendly guide to help people who do not want to learn ''deep'' specifics and terms. Most of this guide will show you copy-paste lines to paste in Terminal, omitting most technical issues. However, you might want to take a look at what SVN is to have a general understanding of this version. If you follow steps correctly, VS should be able to run. ''If you have problems compiling in Ubuntu, post a new thread in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5|VS Forums]. Someone will be able to help you.''
+This is a newb friendly guide to help people who do not want to learn ''deep'' specifics and terms. Most of this guide will show you copy-paste lines to paste in Terminal, omitting most technical issues. However, you might want to take a look at what SVN is to have a general understanding of this version. If you follow steps correctly, VS should be able to run. ''If you have problems compiling in Ubuntu, post a new thread in the [http://forums.vega-strike.org/viewforum.php?f=5|VS Forums]. Someone will be able to help you.''
 Note: This process was done in Ubuntu 8.10 (Intrepid), though it might work in Debian as well. Should be able to work in the Ubuntu derivatives, too.

@@ Line 39: / Line 39: @@
 == Building ==
-You might not understand what building or compiling is, but that is not that important. What ''is'' important is that you do it. Its really not that complicated, so here it goes.
+You might not understand what building or compiling is, but that is not important. What ''is'' important is that you do it. Its really not that complicated, so here it goes.
 * First of all, we have to make sure we have certain minimum requirements. I could list you a dozen ''1337'' terms, but you don't certainly need to know them. We'll just make sure to have them all by inserting this into Terminal (copy and paste entire code into Terminal).
 <pre>sudo apt-get install libpng12-0 libpng12-dev python2.7-dev libexpat1-dev     \

@@ Line 42: / Line 42: @@
 * First of all, we have to make sure we have certain minimum requirements. I could list you a dozen ''1337'' terms, but you don't certainly need to know them. We'll just make sure to have them all by inserting this into Terminal (copy and paste entire code into Terminal).
 <pre>sudo apt-get install libpng12-0 libpng12-dev python2.6-dev libexpat1-dev     \
-         libjpeg62-dev glutg3-dev libopenal-dev libgtk2.0-dev libogg-dev libvorbis-dev \
+         libjpeg62-dev freeglut3-dev libopenal-dev libgtk2.0-dev libogg-dev libvorbis-dev \
          build-essential libgl1-mesa-dev automake autoconf libsdl1.2-dev
 </pre>