VsWiki - User contributions [en]

HowTo:Checkout GIT

2017-02-18T10:28:15Z

Ermo: /* Set up */ Make Boost v1.53 the preferred version

This page describes how to use GIT with the Vega Strike SVN repository.

[http://git-scm.com/ GIT] is a distributed sourcecode revision control system, which allows you to commit changes to a local repository and from there commit the changes to the remove Vega Strike SVN repository.
This is useful if you want to experiment with the codebase, or if you do not have commit privileges to the Vega Strike SVN repository.

If you are unfamiliar with GIT, the you should start by reading the [https://git.wiki.kernel.org/index.php/GitSvnCrashCourse GIT SVN Crash Course].

== Installation ==
First you need to install the GIT and GIT-SVN packages. How you do this, depends on your system.

See the [http://book.git-scm.com/2_installing_git.html chapter 2] in the GIT Book.

== Set up ==
After installing the two packages above, you have to set up a local git repository for the Vega Strike codebase.

Normally git-svn will copy the full svn repository, that is all revisions of all files.
This takes takes a long time, and as you seldom need the full history, you can instead copy from a given revision onwards.

This command will only copy the most recent revision. If you want the full history, remove the "-rHEAD" option:
<pre>
git svn clone -rHEAD https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike/
</pre>

Next you need to handle svn:externals. You can find them with "git svn show-externals". There may be a better way using git submodules, but this works.
<pre>
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_53_0/boost/ boost/1_53/boost
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_53_0/libs/python/src/ boost/1_53/src
</pre>

For older versions of Boost:
<pre>
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_35_0/boost/ boost/1_35/boost
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_35_0/libs/python/src/ boost/1_35/src
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_45_0/boost/ boost/1_45/boost
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_45_0/libs/python/src/ boost/1_45/src
</pre>

We recommend that you add the following lines to your .gitignore file, which should be created in the same directory as the .git directory is located.
<pre>
boost/1_53
boost/1_45
boost/1_35
boost_patched_gcc44
</pre>
You may also want to add auto-generated files to .gitignore.

Now you are almost ready to work on the codebase. You just need to create a branch to work on. This will make it easier to keep your local GIT repository synchronized with the remote SVN repository.

git branch ''insert-your-branch-name''
git checkout ''insert-your-branch-name''

Replace ''insert-your-branch-name'' with the name that you want to call your branch.

From here on, you can follow the normal build instructions.

== Synchronize with SVN ==
If others commit changes to the remote SVN repository, you can update your local GIT repository as follows.

Make sure that you have committed all your changes to the local GIT repository before you start synchronizing.

First you need to update the trunk of your local GIT repository with the changes from the remote SVN repository.

git checkout master
git svn rebase

Next you can synchronize your branch with the trunk.

git checkout ''insert-your-branch-name''
git pull . master

== Submit your changes ==
The "git commit" operation only commits your changes to your local GIT repository. When you want to submit your changes to the remote SVN repository, then you have two options.
If you have commit privileges to the Vega Strike SVN repository, then you can use the "git svn dcommit" command. Otherwise you have to submit a patch to the Vega Strike forums.

You can either use

git diff --no-prefix master..''insert-your-branch-name'' > mypatch.diff

Better yet, you can use the following bash script, which will make sure that the output looks like an SVN patch.
<pre>
#!/bin/sh
#
# git-svn-diff
# Generate an SVN-compatible diff against the tip of the tracking branch
TRACKING_BRANCH=`git config --get svn-remote.svn.fetch | sed -e 's/.*:refs\/remotes\///'`
REV=`git svn find-rev $(git rev-list --date-order --max-count=1 $TRACKING_BRANCH)`
git diff --no-prefix $(git rev-list --date-order --max-count=1 $TRACKING_BRANCH) $* |
sed -e "s/^+++ .*/& (working copy)/" -e "s/^--- .*/& (revision $REV)/" \
-e "s/^diff --git [^[:space:]]*/Index:/" \
-e "s/^index.*/===================================================================/"
</pre>
For a more complete script see [https://gist.github.com/710219 git-svn-diff.sh].

HowTo:Checkout GIT

2017-02-18T10:21:55Z

Ermo: Update link to svn repo

This page describes how to use GIT with the Vega Strike SVN repository.

[http://git-scm.com/ GIT] is a distributed sourcecode revision control system, which allows you to commit changes to a local repository and from there commit the changes to the remove Vega Strike SVN repository.
This is useful if you want to experiment with the codebase, or if you do not have commit privileges to the Vega Strike SVN repository.

If you are unfamiliar with GIT, the you should start by reading the [https://git.wiki.kernel.org/index.php/GitSvnCrashCourse GIT SVN Crash Course].

== Installation ==
First you need to install the GIT and GIT-SVN packages. How you do this, depends on your system.

See the [http://book.git-scm.com/2_installing_git.html chapter 2] in the GIT Book.

== Set up ==
After installing the two packages above, you have to set up a local git repository for the Vega Strike codebase.

Normally git-svn will copy the full svn repository, that is all revisions of all files.
This takes takes a long time, and as you seldom need the full history, you can instead copy from a given revision onwards.

This command will only copy the most recent revision. If you want the full history, remove the "-rHEAD" option:
<pre>
git svn clone -rHEAD https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike/
</pre>

Next you need to handle svn:externals. You can find them with "git svn show-externals". There may be a better way using git submodules, but this works.
<pre>
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_35_0/boost/ boost/1_35/boost
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_35_0/libs/python/src/ boost/1_35/src
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_45_0/boost/ boost/1_45/boost
git svn clone -rHEAD http://svn.boost.org/svn/boost/tags/release/Boost_1_45_0/libs/python/src/ boost/1_45/src
</pre>

We recommend that you add the following lines to your .gitignore file, which should be created in the same directory as the .git directory is located.
<pre>
boost/1_35
boost/1_45
boost_patched_gcc44
</pre>
You may also want to add auto-generated files to .gitignore.

Now you are almost ready to work on the codebase. You just need to create a branch to work on. This will make it easier to keep your local GIT repository synchronized with the remote SVN repository.

git branch ''insert-your-branch-name''
git checkout ''insert-your-branch-name''

Replace ''insert-your-branch-name'' with the name that you want to call your branch.

From here on, you can follow the normal build instructions.

== Synchronize with SVN ==
If others commit changes to the remote SVN repository, you can update your local GIT repository as follows.

Make sure that you have committed all your changes to the local GIT repository before you start synchronizing.

First you need to update the trunk of your local GIT repository with the changes from the remote SVN repository.

git checkout master
git svn rebase

Next you can synchronize your branch with the trunk.

git checkout ''insert-your-branch-name''
git pull . master

== Submit your changes ==
The "git commit" operation only commits your changes to your local GIT repository. When you want to submit your changes to the remote SVN repository, then you have two options.
If you have commit privileges to the Vega Strike SVN repository, then you can use the "git svn dcommit" command. Otherwise you have to submit a patch to the Vega Strike forums.

You can either use

git diff --no-prefix master..''insert-your-branch-name'' > mypatch.diff

Better yet, you can use the following bash script, which will make sure that the output looks like an SVN patch.
<pre>
#!/bin/sh
#
# git-svn-diff
# Generate an SVN-compatible diff against the tip of the tracking branch
TRACKING_BRANCH=`git config --get svn-remote.svn.fetch | sed -e 's/.*:refs\/remotes\///'`
REV=`git svn find-rev $(git rev-list --date-order --max-count=1 $TRACKING_BRANCH)`
git diff --no-prefix $(git rev-list --date-order --max-count=1 $TRACKING_BRANCH) $* |
sed -e "s/^+++ .*/& (working copy)/" -e "s/^--- .*/& (revision $REV)/" \
-e "s/^diff --git [^[:space:]]*/Index:/" \
-e "s/^index.*/===================================================================/"
</pre>
For a more complete script see [https://gist.github.com/710219 git-svn-diff.sh].

HowTo:Compile from SVN on Linux

2015-04-22T17:09:33Z

Ermo: /* With CMake (recommended) */ The correct path to the mesher_tool binary is ./build/objconv/mesh_tool, not ./build/mesh_tool/mesh_tool

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/data)
** code package: '''vegastrike''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)
** '''cmake''' (and '''cmake-curses-gui''' if you want to use more convenient ccmake)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10'''+, this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu,xv}-dev
</pre>

On '''fedora 17/18/19''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

Not strictly necessary, but to get as many used libraries as you can: x11proto-resource-dev libxkbfile-dev libxpm-dev libxres-dev libxv-dev libgtkglext1-dev

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake (recommended) ===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

If for some reason you want to see the compiler commands, you can press ''t'' while in ccmake and toggle the ''CMAKE_VERBOSE_MAKEFILE'' option from ''OFF'' to ''ON'' and press ''c'' to reconfigure and ''g'' to regenerate the ''Makefile''.

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/objconv/mesh_tool # mesh converter, for modding
</pre>

===With Autotools (deprecated) ===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

=== Using Python 3 ===
Install as above <code>libpython3.4 libpython3-all-dev libpython3.4-dbg</code> (not quite necessary, but if you're compiling a development version...)
Then configure VS to use it. Simply typing a different version (e.g. "3.4") in cmake/ccmake is '''not''' enough - it may not even find the right files. Replace "2.7" to "3.4" in specific paths '''PYTHON_'''* paths. But that's not all - '''Boost_PYTHON_LIBRARY_'''* paths point at something like "/usr/lib/x86_64-linux-gnu/libboost_python.so", which is likely to be symlink to a ''Python 2'' library. In this case you'll get lots of errors like
<pre>CMakeFiles/vegaserver.dir/src/cmd/script/director_server.cpp.o:director_server.cpp:(.text+0x139): more undefined references to `boost::python::detail::init_module(PyModuleDef&, void (*)())' follow
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_python.so: undefined reference to `PyString_Size'
</pre> So check what this path really does:
<pre>
$ls -l /usr/lib/x86_64-linux-gnu/libboost_python*
lrwxrwxrwx ... /usr/lib/x86_64-linux-gnu/libboost_python.so -> libboost_python-py27.so
</pre> Now, back in Cmake replace it with whatever link on the list is appropriate for your version ("/usr/lib/x86_64-linux-gnu/libboost_python-py34.so" in our case).

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Edit XMESH files

2015-04-05T18:54:48Z

Ermo: Update to working mesh_xml.cpp code link

{{NAV_Manual |
| previous=[[HowTo:Edit BFXM files|Editing BFXM files (format spec)]]
| up=[[HowTos]]
| next=[[HowTo:Add LODs|Add Levels Of Detail]]
}}
----
You can find a list of all tags supported in xmesh in [http://sourceforge.net/p/vegastrike/code/HEAD/tree/trunk/vegastrike/src/gfx/mesh_xml.cpp this file]. (though it's very cryptic for non-programmers)

==Syntax of a xmesh file (examples are plucked from here and there, for full description see below):==
<pre>
<Mesh texture="texturename.png" sharevertex="1" scale="1.0">
<Points>
<Point>
<Location x="-0.000000" y="0.330000" z="1.500000"/>
<Normal i="-2302.996338" j="-5663.045410" k="-1926.291382"/>
</Point>
<Point>
<Location x="-0.000000" y="-0.330000" z="1.500000"/>
<Normal i="-2302.996338" j="5663.045410" k="-1926.291382"/>
</Point>
.......
</Points>

<Polygons>
<Tri>
<Vertex point="2" s="0.500000" t="0.500000"/>
<Vertex point="1" s="0.000000" t="0.500000"/>
<Vertex point="0" s="0.500000" t="0.000000"/>
</Tri>
<Quad>
<Vertex point="35" s="0.564706" t="0.282353"/>
<Vertex point="37" s="0.627451" t="0.501961"/>
<Vertex point="39" s="0.462745" t="0.498039"/>
<Vertex point="41" s="0.231373" t="0.278431"/>
</Quad>
<Trifan>
<Vertex point="35" s="0.564706" t="0.282353"/>
<Vertex point="37" s="0.627451" t="0.501961"/>
<Vertex point="39" s="0.462745" t="0.498039"/>
<Vertex point="41" s="0.231373" t="0.278431"/>
<Vertex point="39" s="0.462745" t="0.498039"/>
<Vertex point="41" s="0.231373" t="0.278431"/>
</Trifan>
......
</Polygons>

<Logo type="5" rotate="0.000000" size="0.500000" offset="0.010000">
<Ref point="3" weight="1.000000" />
<Ref point="2" weight="1.000000" />
<Ref point="9" weight="1.000000" />
</Logo>
.......

<LOD meshfile="asteroid.lod2.xmesh" size="300"/>
<LOD meshfile="noroids.xmesh" size="25"/>
.....

<Material reflect="0.5" LightningOn="0.5" >
<Diffuse red="1.00000" green="1.00000" blue="1.00000" alpha="1.00000" />
<Ambient red="1.00000" green="1.00000" blue="1.00000" alpha="1.00000" />
<Specular red="1.00000" green="1.00000" blue="1.00000" alpha="1.00000" />
</Material>

</Mesh>
</pre>

==Description of the XMesh file syntax==

<'''Mesh''' ...> </Mesh> - Marks the begin and the end of the mesh(file)
*'''Scale''' - Sets the scaling of the mesh in the game. Values > 1 make the object bigger.
*'''texture0''' - filename of the texture map for the mesh
*'''texture1''' - ('''optional''') like 'texture0', except that it is a reflectivity map. It should look fairly similar to the actual texture, just with different colors. See also VsHowtoAddPerPixelLighting.
*'''texture2''' - ('''optional''') like 'texture0', but this it the damagemap
*'''texture3''' - ('''optional''') like 'texture0', but this is the glowmap
*'''alphamap''' - ('''optional''') This is the map to be used to set the transparency with blendmode="SRCALPHA INVSRCALPHA". It should be in the same format as the alp files (256 colour greyscale) and is used in the same way, with white solid, and black transparent
*'''alphamap2''' - ('''optional''') same as 'alphamap' except for reflectivity.
*'''alphamap3''' - ('''optional''') same as 'alphamap' except for glowmap.
*'''sharevertex''' - ('''optional''') ???????????????
*'''blend''' - ('''optional''') This is the transparency of the mesh.
**'''"ONE ZERO"''' - The mesh will be solid.
**'''"ONE ONE"''' - The mesh will be 50% transparent
**'''"SRCALPHA INVSRCALPHA"''' - The mesh will use the alphamap file to set the transparency.
*'''animation''' - ('''optional''') Allows texture animations. (eg animation="test.ani") See VsHowtoMakeAnimatedTextures. If used it replaces the ''texture'' tag and connected tags.
*'''animation2''' - ('''optional''') Same as animation except for reflectivity. See VsHowtoMakeAnimatedTextures.
*'''animation3''' - ('''optional''') Same as animation except for glowmap.
*<'''Points'''> </Points> - Marks the begin and the end of the point entries.
**<'''Location''' .../> - Location of the point.
***'''x''','''y''','''z''' - Three coordinates of the point in space.
**<'''Normal''' .../> - Normal values
***'''i''','''j''','''k''' - the belonging Normal - Values of the points.
*<'''Polygons'''> </Polygons> - Marks the begin and the end of the polygon entries. Polygon points must be specified in counter clockwise order.
**<'''Tri'''> </Tri> - ('''optional''')(''repeatable'')
***<'''Vertex''' .../> - 3 of this to form a Triangle
****'''point''' - Point number (from Points section)
****'''s''' - texture coordinate (horiz.) at this vertex
****'''t''' - texture coordinate (vert.) at this vertex
**<'''Quad'''> </Quad> - ('''optional''')(''repeatable'')
***<'''Vertex''' .../> - 4 of this to form a Quad
****'''point''' - Point number (from Points section)
****'''s''' - texture coordinate (horiz.) at this vertex
****'''t''' - texture coordinate (vert.) at this vertex
**<'''Trifan'''> </Trifan> - ('''optional''')(''repeatable'')
***<'''Vertex''' .../> - 4 or more of this to form a "fan" of triangles with one common vertex (1) in the following way: Tri 1,2,3; Tri 1,3,4; Tri 1,4,5 etc..
****'''point''' - Point number (from Points section)
****'''s''' - texture coordinate (horiz.) at this vertex
****'''t''' - texture coordinate (vert.) at this vertex
**<'''Line'''> </Line> - ('''optional''')(''repeatable'') - Will draw the face as simple lines (wireframe) without a texture map.
***<'''Vertex''' .../> - an even number of this form seperate lines
****'''point''' - Point number (from Points section)
****'''s''' - N/A
****'''t''' - N/A
*<'''LOD''' .../> - ('''optional''')(''repeatable'') Level Of Detail entry.
**'''meshfile''' - alternate mesh file to be used for this level of detail.
**'''size''' - number of pixels used by the ship at which this LOD cuts in.
*<'''Material''' ...> </Material> - ('''optional''') ?
**'''reflect''' - reflection of environment ('0'=no, '1'=yes). results in a glassy look.
**'''~LightingOn''' - ?
**'''~UseNormals''' - ('''optional''') Define if Vegastrike should use the normals defined in the <Points> section (can be '1' or '0')
**<'''Diffuse''' ... /> - ('''optional''') base color
***'''red''','''green''','''blue''' - 0.0 to 1.0
***'''alpha''' - 0.0 = transparent to 1.0 = opaque
**<'''Ambient''' ... /> - ('''optional''') base color in shadow
***'''red''','''green''','''blue''' - 0.0 to 1.0
***'''alpha''' - ?
**<'''Specular''' ... /> - ('''optional''') color of reflection (requires reflect='1')
***'''red''','''green''','''blue''' - 0.0 to 1.0, high values result in high reflectivity
***'''alpha''' - ?
*<'''Logo''' ... > </Logo> - ('''optional''')(''repeatable'')
**'''type''' - Logotype
***'''0''' - faction logo
***'''1''' - squad logo
***'''2''' - (2 or higher) internal use
**'''rotate''' - How many degrees the logo is rotated.
**'''size''' - Size of the logo.
**'''offset''' - Offset of polygon of logo.
**<'''Ref''' ... /> - ('''optional''')(''repeatable'') The order of the points is supposed to be clockwise. Reversing the order should flip it.
***'''point''' - Insert the point numbers here(the reference points that the logo is weighted against).
***'''weight''' - The weight of the points in weighted average of reference points.
----
{{NAV_Manual |
| previous=[[HowTo:Edit BFXM files|Editing BFXM files (format spec)]]
| up=[[HowTos]]
| next=[[HowTo:Add LODs|Add Levels Of Detail]]
}}

HowTo:Compile from SVN on Linux

2013-07-22T23:51:45Z

Ermo: /* With CMake (recommended) */ add notes on enabling a more verbose build process

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/data)
** code package: '''vegastrike''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10''', this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu,xv}-dev
</pre>

On '''fedora 17/18/19''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake (recommended) ===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

If for some reason you want to see the compiler commands, you can press ''t'' while in ccmake and toggle the ''CMAKE_VERBOSE_MAKEFILE'' option from ''OFF'' to ''ON'' and press ''c'' to reconfigure and ''g'' to regenerate the ''Makefile''.

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===With Autotools (deprecated) ===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2013-07-20T15:29:11Z

Ermo: /* Requirements */ The fedora instructions are good for f19 as well. :)

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/data)
** code package: '''vegastrike''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10''', this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu,xv}-dev
</pre>

On '''fedora 17/18/19''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake (recommended) ===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===With Autotools (deprecated) ===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2013-07-16T19:37:08Z

Ermo: /* With CMake (recommended) */ remove spurious paragraph in the ccmake comments

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/data)
** code package: '''vegastrike''' (repository link: https://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10''', this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu,xv}-dev
</pre>

On '''fedora 17/18''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake (recommended) ===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===With Autotools (deprecated) ===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2013-01-26T17:11:35Z

Ermo: /* With CMake */ Using cmake is recommended as far as I know...

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10''', this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu,xv}-dev
</pre>

On '''fedora 17/18''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake (recommended) ===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit. classic autotools, and the newer (recommended) cmake. I
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===With Autotools (deprecated) ===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2013-01-26T17:11:10Z

Ermo: /* With Autotools */ autotools is not recommended as far as I know...

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10''', this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu,xv}-dev
</pre>

On '''fedora 17/18''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit. classic autotools, and the newer (recommended) cmake. I
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===With Autotools (deprecated) ===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2013-01-21T18:49:53Z

Ermo: /* Requirements */ add libxv-dev to XUbuntu prerequisites

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10''', this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu,xv}-dev
</pre>

On '''fedora 17/18''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit. classic autotools, and the newer (recommended) cmake. I
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===With Autotools===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2013-01-21T14:56:22Z

Ermo: /* Requirements */ Update build prerequisites for fedora and XUbuntu 12.10

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''For specific instructions for Ubuntu see: [[HowTo:Checkout SVN (Ubuntu Linux)]]''

''For windows compiling see: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

On '''Debian''', this probably should do the trick in (copy and paste the into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

On '''XUbuntu 12.10''', this should do the trick (copy and paste into terminal):

<pre>
sudo apt-get install \
build-essential cmake-curses-gui freeglut3-dev python-dev \
lib{expat1,gl1-mesa,gtk2.0,jpeg-turbo8,ogg,openal,png12,sdl1.2,vorbis,xmu}-dev
</pre>

On '''fedora 17/18''', this should do the trick (copy and paste into terminal):

<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Building==

The building and compiling process can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===With CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit. classic autotools, and the newer (recommended) cmake. I
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===With Autotools===
The build procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Custom Makefile creation and usage===
====Configure====
If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://forums.vega-strike.org/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://forums.vega-strike.org/viewtopic.php?t=7562]

====Make====
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://forums.vega-strike.org/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland. 
 
Note: You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error. 
 
Note: If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

====Install====
Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing binary after it's built by the compiler.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

==Setup and run the development version==

===Setup===
This step is not necessary — the binaries should normally figure out where they are with respect to the data directory, but if the version you are using can't do this then you may need to follow these instructions.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegastrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we can create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
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 can normally start ''vegastrike'' from the ''vegastrike'' module you downloaded and built it in.
<pre>~/VegaStrike/vegastrike> ./vegastrike</pre>
Otherwise on other older versions you may have to start it from the ''data'' directory after copying or symbolic linking it as per the earlier instructions.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or desktop menus. Simply find your menu editor and point it to the ''vegastrike'' executable.
* 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 ''data'' 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.

=See also=
{{FIXME}}These links are broken and they are very old from 2003 and most likely becoming irrelevant if someone knows for sure please update the links and put them in the right location, or delete {{FIXME}}
* [http://forums.vega-strike.org/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://forums.vega-strike.org/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2012-11-16T15:59:55Z

Ermo: /* Requirements */ correct package names for X deps

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]], [[HowTo:Checkout SVN (Ubuntu Linux)]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

This probably should do the trick in debian/ubuntu (copy and paste the entire code into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

In fedora 17, this should do the trick (copy and paste into terminal):
<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,xkbfile,Xmu,Xpm,Xres,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Compiling==

Compiling can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===Autotools===
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Installing===

Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing the built binary from the data folder.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2012-11-15T23:13:04Z

Ermo: /* Requirements */ add cmake

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]], [[HowTo:Checkout SVN (Ubuntu Linux)]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

This probably should do the trick in debian/ubuntu (copy and paste the entire code into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

In fedora 17, this should do the trick (copy and paste into terminal):
<pre>
sudo yum install \
automake cmake gcc gcc-c++ glibc-devel kernel-devel make \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,Xkbfile,Xmu,Xpm,XRes,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Compiling==

Compiling can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===Autotools===
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Installing===

Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing the built binary from the data folder.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2012-11-15T21:31:32Z

Ermo: /* Requirements */ include X11 deps

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]], [[HowTo:Checkout SVN (Ubuntu Linux)]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

This probably should do the trick in debian/ubuntu (copy and paste the entire code into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

In fedora 17, this should do the trick (copy and paste into terminal):
<pre>
sudo yum install \
make automake gcc gcc-c++ glibc-devel kernel-devel \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}-devel \
lib{X11,Xdmcp,Xkbfile,Xmu,Xpm,XRes,XScrnSaver,Xtst,Xv,Xxf86misc}-devel
</pre>

==Compiling==

Compiling can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===Autotools===
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Installing===

Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing the built binary from the data folder.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2012-11-15T19:25:13Z

Ermo: /* Compiling */ sp.

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]], [[HowTo:Checkout SVN (Ubuntu Linux)]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

This probably should do the trick in debian/ubuntu (copy and paste the entire code into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

In fedora 17, this should do the trick (copy and paste into terminal):
<pre>
sudo yum install \
make automake gcc gcc-c++ glibc-devel kernel-devel \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}{,-devel}
</pre>

==Compiling==

Compiling can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===Autotools===
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Installing===

Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing the built binary from the data folder.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2012-11-15T19:23:53Z

Ermo: /* Requirements */ Add build prerequisites for fedora 17

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]], [[HowTo:Checkout SVN (Ubuntu Linux)]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1 or above
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''
** '''libfreeimage3''' (vegastrike itself can compile without it, but mesher can't)

This probably should do the trick in debian/ubuntu (copy and paste the entire code into terminal):

<pre>
sudo apt-get install libpng12-0 libpng12-dev python-dev libexpat1-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>

In fedora 17, this should do the trick (copy and paste into terminal):
<pre>
sudo yum install \
make automake gcc gcc-c++ glibc-devel kernel-devel \
{python,expat,freealut,freeglut,gtk2,libjpeg-turbo,libpng,libvorbis,openal-soft,SDL}{,-devel}
</pre>

==Compiling==

Complining can be accomplished with two systems as of now. There's the classic autotools, and the newer (recommended) cmake. If you have cmake installed, you should try it.

===CMake===

Building with CMake is just building with Make, only the configure part can be done interactively, and all intermediate files are tidily put in their own folders:

<pre>
cd ./vegastrike
mkdir build
cd build
ccmake .. # this will pop up an interactive configuration screen, press "c" to autoconfigure,
# and once it's done "g" to generate everything and exit.
# Or edit stuff and follow on-screen instructions if you know what you're doing.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./build/vegastrike # to play the game
./build/vegastrike --debug=3 # to generate detailled logs for bug reporting
./build/setup/vssetup # to edit game settings
./build/mesh_tool/mesh_tool # mesh converter, for modding
</pre>

===Autotools===
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-flags='-O3 -g' # or --enable-debug to disable optimization. -ffast-math will cause problems in code that checks for infinities. Note that in the first flag there's a capital 'o', not a zero.
make
</pre>

Now you can run from the build folder:

<pre>
cd ./vegastrike
./vegastrike # to play the game
./vegastrike --debug=3 # to generate detailled logs for bug reporting
./vssetup # to edit game settings
./mesher # mesh converter, for modding
</pre>

===Installing===

Installing is not really necessary to play, but you can do it if you wish to have the game accessible to all users. Otherwise, you can play by executing the built binary from the data folder.

If you do want to install, you'll need root access:

<pre>
sudo make install
</pre>

If you plan to install, when you're configuring:

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</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 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.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
The final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

If you receive error without any mention of missing library (or something like) after very long line about running g++, try to set proper permissions or simply force your way through it and see whether it's your problem (if you're superuser). It looks like that:
<pre>
collect2: ld returned 1 exit status
make[1]: *** [vegastrike] Error 1
make[1]: Leaving directory `/home/username/Games/VegaStrike/vegastrike'
make: *** [all] Error 2
~/Games/VegaStrike/vegastrike$ sudo make
</pre>

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?f=2&t=10990 "Ubuntu problems" thread in the forum] - more about little troubles linuxoids can encounter.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]