HowTo:Checkout SVN - Revision history

Karmann: /* Determining when compiling is required */ change external-type links to internal pages to regular wikilinks

2013-08-06T01:30:54Z

‎Determining when compiling is required: change external-type links to internal pages to regular wikilinks

Tbeholder at 22:44, 29 June 2013

2013-06-29T22:44:53Z

Tbeholder at 22:32, 29 June 2013

2013-06-29T22:32:58Z

Iansterguy: /* Determining when compiling is required */ Even better differentiated where to find further instructions by adding on the spot links.

2013-02-24T19:41:28Z

‎Determining when compiling is required: Even better differentiated where to find further instructions by adding on the spot links.

Iansterguy: /* Determining when compiling is required */ Clarified which instructions refered to.

2013-02-24T19:34:04Z

‎Determining when compiling is required: Clarified which instructions refered to.

Iansterguy: Added header "Destribution specific" and moved "Ubuntu Specific" to the top, where it may save the reader effort.

2013-02-24T19:24:56Z

Added header "Destribution specific" and moved "Ubuntu Specific" to the top, where it may save the reader effort.

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

2013-01-08T21:29:01Z

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

Iansterguy: /* Usage */ Shortened section name to checkout and put related sections under branch.

2012-12-22T09:19:34Z

‎Usage: Shortened section name to checkout and put related sections under branch.

Iansterguy: /* Determining when compiling is required */ moved compileing notes to "HowTo:Compile_from_SVN#Make"

2012-12-22T08:50:54Z

‎Determining when compiling is required: moved compileing notes to "HowTo:Compile_from_SVN#Make"

Iansterguy: /* Boost Specific Check-out */ Put the code in a code box and adjusted text

2012-12-22T07:45:47Z

‎Boost Specific Check-out: Put the code in a code box and adjusted text

@@ Line 165: / Line 165: @@
 * If something only changed in the ''data'' package, you don't need to recompile.
 * If something changed in the source code package ''vegastrike'' you must compile.
-From here on either follow the common compiling instructions from this link [http://wiki.vega-strike.org/HowTo:Compile_from_SVN HowTo:Compile_from_SVN_on_Linux], or follow the specific compiling instructions for your specific Linux distribution to build, setup, and run the game listed under [http://wiki.vega-strike.org/HowTo:Checkout_SVN#Distribution_Specific_Instructions Distribution_Specific_Instructions].
+From here on either follow the common compiling instructions from this link [[HowTo:Compile from SVN on Linux]], or follow the specific compiling instructions for your specific Linux distribution to build, setup, and run the game listed under [[HowTo:Checkout SVN#Distribution Specific Instructions]].
 ==RabbitVCS==

@@ Line 89: / Line 89: @@
 The following syntax...
 <pre>
-  svn co --ignore-externals https://svn.code.sf.net/p/vegastrike/code/trunk vegastrike
+  svn checkout http://svn.code.sf.net/p/vegastrike/code/trunk vegastrike-code
 </pre>
-...will download the entire tree (all modules) into directory `vegastrike'. But '''don't do this'''! Such a command would download data for both the normal and ogre branches, plus Visual Studio projects for ALL supported versions and goodness knows what else.
+...will download the entire tree (all modules) into directory `vegastrike-code'. But '''don't do this'''! Such a command would download data for both the normal (4 copies of it - in /data, /win-32, /win-64 and /mac) and ogre branches, plus Visual Studio projects for ALL supported versions and goodness knows what else.
 You should really only download individual modules, and a similar syntax can be used. For example, to download the data module...
 <pre>
-  svn co https://svn.code.sf.net/p/vegastrike/code/trunk/data data
+  svn co http://svn.code.sf.net/p/vegastrike/code/trunk/data data
 </pre>
 ...will suffice. (Leaving off the target directory will make svn try check out into the ''working directory''.)
 In order to get all the files required to compile the game, checkout the following modules:
-* data
+* '''data'''
-* vegastrike
+* '''vegastrike'''
 ===Usage===

@@ Line 54: / Line 54: @@
 * '''ogre_branch''' - the old OGRE branch.
-You may download the old OGRE branch including the data6.x dir using this URL: http://vegastrike.svn.sourceforge.net/svnroot/vegastrike/branches/ogre_branch/
+You may download the old OGRE branch including the data6.x dir using this URL: http://svn.code.sf.net/p/vegastrike/code/branches/ogre_branch/
@@ Line 62: / Line 62: @@
 -------------------------------------------
-The Subversion tree can be browsed via a web interface: http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/
+The Subversion tree can be browsed via a web interface: http://sourceforge.net/p/vegastrike/code/
@@ Line 89: / Line 89: @@
 The following syntax...
 <pre>
-  svn co --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk vegastrike
+  svn co --ignore-externals https://svn.code.sf.net/p/vegastrike/code/trunk vegastrike
 </pre>
 ...will download the entire tree (all modules) into directory `vegastrike'. But '''don't do this'''! Such a command would download data for both the normal and ogre branches, plus Visual Studio projects for ALL supported versions and goodness knows what else.
@@ Line 95: / Line 95: @@
 You should really only download individual modules, and a similar syntax can be used. For example, to download the data module...
 <pre>
-  svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data data
+  svn co https://svn.code.sf.net/p/vegastrike/code/trunk/data data
 </pre>
 ...will suffice. (Leaving off the target directory will make svn try check out into the ''working directory''.)
@@ Line 125: / Line 125: @@
 * Download (check-out) the source code package ''vegastrike'', and the content package ''data'' package. Copy and paste, ''in order''.
-<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
 then
-User@UserMachine:~/VegaStrike$ svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data</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.
@@ Line 136: / Line 136: @@
 * For no Boost:
-<pre>svn co --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike vegastrike</pre>
+<pre>svn co --ignore-externals https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike vegastrike</pre>
 <br>
 * If you want 1.35:
@@ Line 146: / Line 146: @@
 You have to check it out of svn and put it next to data.   So if data is in /usr/local/games/vegastrike You would:
-<pre>svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/hqtextures /usr/local/games/vegastrike/hqtextures</pre>
+<pre>svn co https://svn.code.sf.net/p/vegastrike/code/trunk/hqtextures /usr/local/games/vegastrike/hqtextures</pre>
 To be sure that hq textures is being used, check for the message about finding HQ Texture Pack at the start of the console output when running vegastrike.
@@ Line 179: / Line 179: @@
 * Input the URL of the repository into the dialogue box:
 <pre>
-https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
+https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike
 </pre>
 * Click OK to begin checkout of the module.
@@ Line 186: / Line 186: @@
 * Input the URL of the second repository into the dialogue box:
 <pre>
-https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data
+https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike/data
 </pre>
 [You may also alternatively use the built-in repository browser to select a different module you wish to check out.]
@@ Line 207: / Line 207: @@
 Some people have problems with the latest executable relating to Visual C++ 8.  If you want an older version of the executable compiled with VC7, you can browse the repository here:
-http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/win32/bin/vegastrike.exe?view=log
+https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike/win32/bin/vegastrike.exe?view=log
 ==Tortoise SVN==
@@ Line 226: / Line 226: @@
 * Input the URL of the repository into the dialog box:
 <pre>
-   https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
+   https://svn.code.sf.net/p/vegastrike/code/trunk/win32
 </pre>
 [You may also use the built-in repository browser to select the module you wish to check out.]

@@ Line 162: / Line 162: @@
 * If something only changed in the ''data'' package, you don't need to recompile.
 * If something changed in the source code package ''vegastrike'' you must compile.
-From here on either follow the common compiling instructions from the following link, or follow the specific compiling instructions for your specific Linux distribution to build, setup, and run the game listed at the top of the page. [[http://wiki.vega-strike.org/HowTo:Compile_from_SVN HowTo:Compile_from_SVN_on_Linux]]
+From here on either follow the common compiling instructions from this link [http://wiki.vega-strike.org/HowTo:Compile_from_SVN HowTo:Compile_from_SVN_on_Linux], or follow the specific compiling instructions for your specific Linux distribution to build, setup, and run the game listed under [http://wiki.vega-strike.org/HowTo:Checkout_SVN#Distribution_Specific_Instructions Distribution_Specific_Instructions].
 ==RabbitVCS==

@@ Line 162: / Line 162: @@
 * If something only changed in the ''data'' package, you don't need to recompile.
 * If something changed in the source code package ''vegastrike'' you must compile.
-From here on follow the general or specific compiling instructions for your Linux distribution to build, setup, and run the game. [[http://wiki.vega-strike.org/HowTo:Compile_from_SVN HowTo:Compile_from_SVN_on_Linux]]
+From here on either follow the common compiling instructions from the following link, or follow the specific compiling instructions for your specific Linux distribution to build, setup, and run the game listed at the top of the page. [[http://wiki.vega-strike.org/HowTo:Compile_from_SVN HowTo:Compile_from_SVN_on_Linux]]
 ==RabbitVCS==

@@ Line 68: / Line 68: @@
 =Linux Clients=
 ==Command-line svn==
@@ Line 192: / Line 197: @@
 After downloading both vegastrike and data directories, the program must be compiled because some of the source code is in a compiled only language. From here follow the general or specific compiling instructions for your Linux distribution to build, setup, and run the game. [[http://wiki.vega-strike.org/HowTo:Compile_from_SVN HowTo:Compile_from_SVN_on_Linux]]
 =Windows Clients=

@@ Line 114: / Line 114: @@
 Optionally to save on download bandwidth and to possibly download faster, you can download a compressed snapshot of the SVN module, and then just update that to the current revision. Otherwise SVN will get each file individually. To avoid any complication, it will work fine to follow the instruction below, using svn to do the whole checkout.
-Snapshots available here: http://vegastrike.sourceforge.net/forums/viewtopic.php?t=6749.<br>
+Snapshots available here: http://forums.vega-strike.org/viewtopic.php?t=6749.<br>
 Also here: http://sourceforge.net/project/showfiles.php?group_id=181552&package_id=211092&release_id=463105.<br>
 {{Fixme}}(Not sure if this second one includes the hidden .svn directories needed to update it with svn)

@@ Line 109: / Line 109: @@
 Note for newbs: The directory ''is case sensitive''. If you type: cd vegastrike or Vegastrike, it won't find the directory.
-====Basic Check-out====
+====Check-out====
 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.
@@ Line 127: / Line 127: @@
 ''Note:'' If you are having problems with SVN due to connecting via a proxy, try to solve them using the method described here: http://subversion.apache.org/faq.html#proxy
-====Boost Specific Check-out====
+=====Boost Specific Check-out=====
 As of 0.5.1 you will be able to choose not to download the boost revisions included in the vegastrike module.  The Boost revisions are external definitions, so including the --ignore-externals argument when checking out vegastrike will result in none of the boost revisions from downloading.   This greatly reduces your download time. If you dont have a system installed boost setup with boost-python, you can pull the specific version of boost you want (1.28 or 1.35) by updating that directory specifically.
@@ Line 137: / Line 137: @@
 Now, you have to supply ./configure with a specific boost rev when you are choosing anything other than 1.28.   Also, choosing a boost rev that you haven't downloaded yet would be problematic.   If none are to be downloaded, use --with-boost=system, when using system boost, you have to make sure the python version ./configure uses matches the one boost-python was linked with. Some distros will supply multiple boost revs, python revs, but only one rev combo for boost-python.
-====Optional high quality textures====
+=====Optional high quality textures=====
 As of 0.5.1 there is a module in svn called ''hqtextures''. hqtextures, is an optional high quality texture pack that will override the textures in data that exist in hqtextures.  These are jpegs that wont be compressed in-game. Prior to 0.5.1, you have to edit the config file by hand to uncomment the line that enables the hqtextures module. At 0.5.1, it should be a setting in vssetup.   Enabling it while not having it downloaded wont hurt anything.

@@ Line 154: / Line 154: @@
 ====Determining when compiling is required ====
-After downloading all of the files and folders you need in the vegastrike, data, and other directories, the program must be compiled because some of the source code is in a compiled only language. If you only updated the modules in some situations this is not required:
+After downloading all of the files and folders you need in the vegastrike, data, and other directories for the first time the program must be compiled, because some of the source code is in a compiled only language. If you only updated the modules, in some situations compiling again is not required:
 * If something only changed in the ''data'' package, you don't need to recompile.
-* If something changed in the source code package ''vegastrike'' you need to compile. Follow the building part in the Compile_from_SVN_on_Linux compiling instructions. Also follow the instructions to create symbolic links, other wise every time you must follow the "copying or moving procedure for the executables" in the "setup" part of the compiling instructions{{Fixme}}Is this true, it needs to be verified {{Fixme}}.   You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error.
+* If something changed in the source code package ''vegastrike'' you must compile.
 From here on follow the general or specific compiling instructions for your Linux distribution to build, setup, and run the game. [[http://wiki.vega-strike.org/HowTo:Compile_from_SVN HowTo:Compile_from_SVN_on_Linux]]