User:Wirser:wcudir - Revision history

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

2013-01-08T21:31:56Z

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

wirser at 00:59, 2 September 2006

2006-09-02T00:59:45Z

wirser at 00:56, 2 September 2006

2006-09-02T00:56:58Z

wirser at 00:32, 2 September 2006

2006-09-02T00:32:07Z

wirser at 00:19, 2 September 2006

2006-09-02T00:19:32Z

wirser: /* Compile the Vega Strike sourcecode */

2006-09-02T00:18:17Z

‎Compile the Vega Strike sourcecode

wirser at 00:06, 2 September 2006

2006-09-02T00:06:10Z

wirser: /* Game HowTos */

2006-09-01T23:52:53Z

‎Game HowTos

wirser at 23:44, 1 September 2006

2006-09-01T23:44:38Z

wirser at 23:30, 1 September 2006

2006-09-01T23:30:14Z

@@ Line 142: / Line 142: @@
 ~/VegaStrike/vegastrike> make vegastrike
 ~/VegaStrike/vegastrike> make soundserver</pre>
-You will likely receive some error messages during any of these stages, especially during the configure part. If they tell you that your system is missing some development libraries install them. How this is done depends strongly on your Linux distribution, but we will assist you in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5 Compiling Problems forums]. You will be left with a file called "config.log" please attach that instead of copy-and-pasting thousands of lines of error messages. It's all in this file.
+You will likely receive some error messages during any of these stages, especially during the configure part. If they tell you that your system is missing some development libraries install them. How this is done depends strongly on your Linux distribution, but we will assist you in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems forums]. You will be left with a file called "config.log" please attach that instead of copy-and-pasting thousands of lines of error messages. It's all in this file.
 After you installed the missing libraries repeat the last (failed) step and continue.

@@ Line 1: / Line 1: @@
 If you're interested in an experimental version of Vega Strike, then SVN is what you'll be looking at.
@@ Line 158: / Line 146: @@
 After you installed the missing libraries repeat the last (failed) step and continue.
 Finally, there will be two executables called ''vegastrike'' and ''soundserver''.
 =Using GDB with Vegastrike=

@@ Line 10: / Line 10: @@
 ** [[#Using_GDB_with_Vegastrike|Debugging on Linux using GDB]]
 ** [[#Using_Dr_Watson_with_Vegastrike|Debugging on Windows using Dr Watson]]
 =Linux Clients=
@@ Line 60: / Line 92: @@
 ''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.tigris.org/faq.html#proxy
@@ Line 155: / Line 145: @@
 ==Other==
 *[http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ svnX]
 =Using GDB with Vegastrike=
 This page provides information on how to use GDB to help debug Vegastrike.
@@ Line 190: / Line 194: @@
 Then you should get a log produced when Vegastrike crashes.  Please submit this with your bug report.
 ----

@@ Line 1: / Line 1: @@
 * [[HowTo:VCPP Compiling|Compiling from SVN under Visual C++]]
 * [[HowTo:Cygwin Compiling|Compiling from SVN under Cygwin]]
@@ Line 13: / Line 11: @@
 ** [[#Using_Dr_Watson_with_Vegastrike|Debugging on Windows using Dr Watson]]
 =Linux Clients=
@@ Line 97: / Line 60: @@
 ''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.tigris.org/faq.html#proxy
 ===Building===
 *To build the engine, change into the source code directory ''vegastrike''.
@@ Line 191: / Line 155: @@
 ==Other==
 *[http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ svnX]
 ----

@@ Line 1: / Line 1: @@
-[[Category:HowTo]]
 == Compile the Vega Strike sourcecode ==
 * [[HowTo:VCPP Compiling|Compiling from SVN under Visual C++]]

← Older revision		Revision as of 00:06, 2 September 2006
Line 48:		Line 48:

	Then you should get a log produced when Vegastrike crashes. Please submit this with your bug report.		Then you should get a log produced when Vegastrike crashes. Please submit this with your bug report.
		+	=Linux Clients=
		+
		+	==Command-line svn==
		+
		+	===Website===
		+	http://subversion.tigris.org/
		+
		+	===Description===
		+	The linux-command `svn' is the most basic Subversion client.
		+
		+	===Using svn for downloading vs-devel===
		+	Downloading the Vega Strike svn-modules is easy. The general syntax is
		+	<pre>
		+	svn co [repo]/trunk/[module] [target-directory]
		+	</pre>
		+
		+	<pre>
		+	svn co https://svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike vegastrike
		+	</pre>
		+	...will download the entire tree into directory `vegastrike'. In order to download single modules, a similar syntax can be used. For example, to download the data4.x-module,
		+	<pre>
		+	svn co https://svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x data4.x
		+	</pre>
		+	...will suffice.
		+	In order to get all the files required to compile the game, checkout the following modules:
		+	* data4.x
		+	* vegastrike
		+	* music (optional)
		+
		+
		+	==Tutorial to download, setup and run the development version==
		+	In order to run the development version of Vega Strike the executables expect to find the data and music to be in certain places relative to them. This short tutorial deals with these specifics on Linux operating systems. (It also applies for Mac OS X users.)
		+
		+	So, let's start.
		+	* Create a directory where you would like your copy of the Vega Strike development version to live in. For example purposes we will create a directory called ''VegaStrike'' in our user's home-directory.
		+	<pre>~> mkdir VegaStrike</pre>
		+	* Change into this newly created directory. In our case:
		+	<pre>~> cd VegaStrike</pre>
		+
		+	===Initial downloading (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.
		+	* Download (check-out) the source code package ''vegastrike'', the content package ''data4.x'' and the optional ''music'' package.
		+	<pre>~/VegaStrike> svn co https://svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
		+	~/VegaStrike> svn co https://svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x
		+	~/VegaStrike> svn co https://svn.sourceforge.net/svnroot/vegastrike/trunk/music</pre>
		+	This leaves you with three new directories inside your Vega Strike directory called as the packages are.
		+
		+	''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.tigris.org/faq.html#proxy
		+
		+	===Building===
		+	*To build the engine, change into the source code directory ''vegastrike''.
		+	<pre>~/VegaStrike> cd vegastrike</pre>
		+	*Now start with setting up and configuring the build and finally building the engine.
		+	<pre>~/VegaStrike/vegastrike> ./bootstrap-sh
		+	~/VegaStrike/vegastrike> ./configure
		+	~/VegaStrike/vegastrike> make vegastrike
		+	~/VegaStrike/vegastrike> make soundserver</pre>
		+	You will likely receive some error messages during any of these stages, especially during the configure part. If they tell you that your system is missing some development libraries install them. How this is done depends strongly on your Linux distribution, but we will assist you in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5 Compiling Problems forums]. You will be left with a file called "config.log" please attach that instead of copy-and-pasting thousands of lines of error messages. It's all in this file.
		+
		+	After you installed the missing libraries repeat the last (failed) step and continue.
		+	Finally, there will be two executables called ''vegastrike'' and ''soundserver''.
		+
		+	===Setup===
		+	To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, they reside in the source code directory. But they have to be run out of the ''data4.x'' directory. Therefore, we will create a link.
		+	* Change in to the ''data4.x'' directory. (We are still in the source code directory ''vegastrike''.)
		+	<pre>~/VegaStrike/vegastrike> cd ../data4.x</pre>
		+	* Create symbolic links to the executables in the source code directory.
		+	<pre>~/VegaStrike/data4.x> ln -s ../vegastrike/vegastrike
		+	~/VegaStrike/data4.x> ln -s ../vegastrike/soundserver</pre>
		+	If we had made copies or moved the files instead of symbolic linking, we would have to do the procedure of copying or moving every time we build the executables from source.
		+
		+	===Running and configuring===
		+	* To run Vega Strike you have to start it from the ''data4.x'' directory.
		+	<pre>~/VegaStrike/data4.x> ./vegastrike</pre>
		+	* Optionally you can create a short cut to this application onto your desktop or in your start menu. Simply point it to the ''vegastrike'' executable in the ''data4.x'' directory.
		+	* If you need to adjust screen resolutions, input devices and key-mappings, do so by editing the configuration file ''vegastrike.config''. The default configuration file resides in the ''data4.x'' directory. You can change that or you can make your own user specific version by first copying it into your ''.vegastrike'' (hidden directory) directory in your user's home directory.
		+
		+	===Known bugs and work-arounds===
		+
		+
		+	===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.
		+	* Change into the package's directory you want to update. In our example all the packages were stored in a directory called ''VegaStrike''. Let's assume we want to update the ''data4.x'' package.
		+	<pre>~> cd VegaStrike
		+	~/VegaStrike> cd data4.x</pre>
		+	* Update from the SVN repository.
		+	<pre>~/VegaStrike/data4.x> svn update</pre>
		+	* Do this for every package you want to update. Exchange ''data4.x'' with ''vegastrike'' or ''music''.
		+	* If something changed in the ''data4.x'' or the ''music'' package, you don't need to recompile.
		+	* If something changed in the source code package ''vegasstrike''. You only need to repeat the building part of this tutorial.
		+
		+
		+	=Windows Clients=
		+
		+	==Tortoise SVN==
		+
		+	===Website===
		+	http://tortoisesvn.tigris.org/
		+
		+	===Description===
		+	Just like TortoiseCVS, Tortoise SVN lets you work with files under SVN version control directly from Windows Explorer. It's freely available under the GPL.
		+
		+	With TortoiseSVN you can directly check out modules, update, commit and see differences by right clicking on files and folders within Explorer. You can see the state of a file with overlays on top of the normal icons within Explorer. It even works from within the file open dialog.
		+
		+	===Usage===
		+	* Download and Install Tortoise SVN from http://tortoisesvn.tigris.org
		+	* Create a new folder in Windows Manager where you will download your modules (called Sandbox, SVN or similar working location name);
		+	* Within that folder, create another folder being the name of module you wish to checkout e.g. data4.x, music, vegastrike etc;
		+	* Right click on the folder created and select SVN Checkout. This brings up the checkout configuration screen;
		+	* Input the URL of the repository into the dialog box, for example data4.x will be;
		+	<pre>
		+	https://svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x
		+	</pre>
		+	**You may also use the built-in repository browser to select the module you wish to check out.
		+	* Click OK to begin checkout of the module.
		+
		+
		+	=Mac OS X Clients=
		+
		+	==Command Line Client==
		+
		+	===Website===
		+	http://metissian.com/projects/macosx/subversion/
		+
		+	(or http://pdb.finkproject.org/pdb/search.php?summary=svn for Fink packages.)
		+
		+	==SCPlugin==
		+
		+	===Website===
		+	http://scplugin.tigris.org/
		+
		+	===Description===
		+	"The goal of the SCPlugin project is to integrate Subversion into the Mac OS X Finder. The inspiration for this project came from the TortoiseSVN project."
		+
		+	====Usage====
		+	Must have command line client installed.
		+
		+	{{Fixme}}-WRITEME
		+
		+	*[http://www.joshbuhler.com/2005/07/05/setting-up-the-subversion-client-on-mac-os-x/ A good tutorial on setting up SVN for OSX]
		+
		+	==Other==
		+	*[http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ svnX]
		+
		+
		+	----

@@ Line 6: / Line 6: @@
 * [[HowTo:vsCygwin Compiling|Compiling from SVN under Cygwin]]
 * [[HowTo:vsFedora Compiling|Compiling from SVN under Fedora Core]]
 * Debug a Vega Strike Compilation
 ** [[#Using_GDB_with_Vegastrike|Debugging on Linux using GDB]]