VsWiki - User contributions [en]

DOXYGEN DOCUMENTATION

2015-05-30T13:16:27Z

Ezee:

Here you will find the engine's source code documentation produced by Doxygen .

Each release of the engine will have his own doc .

--------------------------------------------------------------------------------
[http://vegastrikevo.sourceforge.net/vegaevo_doc/html/index.html vegastrike-src-0.5.1.r1 Doc]

DOXYGEN DOCUMENTATION

2015-05-30T13:13:31Z

Ezee: link was broken , fixed !

DOCs

2015-05-30T13:12:18Z

Ezee: the links are dead , so ripped

== Engine Documentation for Modders ==

If you're a modder and looking for engine info, this is the place. If it looks incomplete, casual, apathetic, it's because it is. Well, this is better than what there was before... zip nothing. Hopefully this WIKI section will grow, grow, and then grow some more, until it catches up with the vegastrike engine. In the meantime, there's a slight chance you might find what you're looking for here. If not, probably the best way to go is to edit this page to add the section or category you're interested in, put whatever data you can find in it, and then ask the devs to fill in the rest.

[[CONFVAR]] - Configuration variables in vegastrike.config

[[CPPPY]] - C++ functions available to Python

[[CPPCODE]] - C++ code organization, data flow charts, time charts

[[DOXYGEN DOCUMENTATION]] - C++ source code documentation, in .html format

Development:Network:Todo

2014-04-26T15:05:45Z

Ezee: /* Network TODO */

= Bugs for deathmatch =
* With renamed units (renamed aeon in both test2 savegame files, Player 2 seems to load fine, but cannot fire guns.
** Yes. This is a feature, not a bug. The way it sends saved games is by starting with the original entry in units.csv. If that does not exist, it sends a blank CSV file to the clients. [[User:ace123|Patrick]] 02:28, 29 July 2007 (PDT)
* Asteroids not always networked... Space junk doesn't display the cargo type because of the way it was created....

= Network TODO =

List of stuff to be done (that is... the to do in "TODO")
Update of April 2014 :

2 members are working at the MMO Development :

*Eye~R ( hosting , gameplay designer )
*Ezee ( Dev , graphics , gameplay )

Eye~R wrote a first TODO list , because of " '''There's still a lot to do'''. " :

== Vegastrike MMO Server ToDo list: ==

== Vegaserver: ==

Fix "turrets"
Fix owning >1 ship = player dies

== Account Server: ==

Python:

PHP:
Make the fuckin thing talk to MySQL =(

== Website: ==

Pretty frontend, user signup and general website

Home page

About page

Signup page

Login Page

== Admin control interface ==

Ability to review users logged in and evict

Ability to maintain blocklist (may tie this directly into the firewall)

Ability to perform basic admin of user accounts (issue password reset request to previously defined email, alter applicaable email, add user to blocklist)

Ability to perform basic admin of server

== User control interface ==

Ability to change contact Email

Ability to change alternate contact details

Abiltiy to change about

Abiltiy to upload avatar

Ability to upload personal livery

Ability to maintain friends/contacts

== DataBase: ==

Bases table

user table

Add fields for signup IP, last logged in IP and last 10 unique IP's

Add field for email used in signup

Add field for date/time of signup.

Add field for current email, to be used possibly for sending auth code to confirm human signup

Add fields for optional alternate contact details, and an "about" section for profile

Add fields for rank and for faction(default Unadorned)

Add field for IsSuper to indicate SuperUser

Add field for IsFaction to denote Faction Leader status

Add field for Ship (possibly better in accounts?)

account table

Possibly split CSV into applicable fields? will make tweaking of any particular value "easier"..

== Markets: ==

Create sensible "production Tree"

== NEW : DATABASE FOR ACCOUNT SERVER ==

Current user_table:

<nowiki>+---------------+-----------------+------+-----+-----------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------------+-----------------+------+-----+-----------+-------+
| username | varchar(20) | YES | | NULL | |
| user_id | varchar(20) | YES | PRI | NULL | Auto-Increment |
| user_password | varchar(50)| YES | | NULL | |
+---------------+-------------+------+-----+---------+-------+</nowiki>

Proposed:

+---------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------------+-------------+------+-----+---------+-------+
| username | varchar(20) | YES | | NULL | |
| user_id | varchar(20) | YES | | NULL | |
| user_password | varchar(50) | YES | | NULL | |
| signup_mail | varchar(30)| YES | | NULL | |
| timedate_stamp | date(30)|YES| | NULL | |
| user_mail | varchar(30)|YES| | NULL | |
| signup_ip | varchar(12)|YES| | NULL | |
| current_ip | varchar(12)|YES| | NULL | |
| known_ip | varcahr(120)|YES| | NULL | |
| issuper | int(1) | NO | | 0 | |
| isfaction | int(1) | NO | | 0 | |
| rank | varchar(20)|YES| | NULL | |
| ship | varchar(30)|YES| | NULL | |
| alt_contact| varchar(180)| YES | | NULL | |
| about | varchar(1000)| YES | NULL | |
+---------------+-------------+------+-----+---------+-------+

== CMD_CARGOUPGRADE and other Docking-related stuff ==
* Client basecomputer notifications are bad:
** Whenever anyone docked at ({{Fixme}}: any????) base buys or sells cargo/upgrade, the menu for all other players resets to the top level...
** Needs to keep menu open but still keep cargo in sync.
* To do much much later: Buying ships, missions, saving/loading from COMPY interface.
* Cargo salvage boxes - tractor beams?

== More bugs ==
* There are two different functions to send damage, and I have seen three distinct error messages in a few cases (?!?!?!)
** zonemgr.cpp:614, broadcastDamage AS WELL AS zonemgr.cpp:538, addPosition CALLS zonemgr.cpp:688, addDamage
** netserver_devices.cpp:136, sendDamages CALLED FROM Unit::ApplyLocalDamage

== Other synchronization bugs ==
* Saving games: WriteSavedGame() being used to send ADDCLIENT messages to other players, but original saved game used for player himself.

== Some other bug I wrote down, probably doesn't belong here: ==
* Gas Giant ice rings appear in front of the planet - z buffer.

== General list ==

* Clean up server-client-authserver communication
** I would really like if the messages sent and received could be done in a more uniform way.
** Clean up some unused messages.
* Login:
** Encrypted authentication, possibly using a random server token.
*** This means that login data cannot be the first packet sent -- it must first negotiate a key.
** Would SSL be a good idea here. I think we currently link with a Crypto++ library... but I'm not sure how it is currently used or how to use it.
** Make sure authserver-server-client time synchronization works correctly. Maybe every few minutes (or even hours) A,S,C should sync in case a clock gets off somehow.
* Damage:
** Theoretically implented, but I have yet to see collisions and weapons actually do damage client-side.
*** The problem is: Clients are responsible for position, so they often bounce before the server has a chance to give damage. Other times you die because the client doesn't respond fast enough! [[User:ace123|Patrick]] 20:04, 24 February 2007 (PST)
** Not sure what CMD_SCAN is to be used for... it's used in one place -- that is in NetClient::scanRequest.
** I don't know yet how a MMORPG would implement dying...
*** It would be bad to have to start from scratch every time you crash into something.
*** Have the respawn key re-join?
*** Right now you save only if you disconnect without dying. I guess that works.
*** How do we implement saving? Respawn doesn't work without a way to save... or should you keep everything the same as when you died, and then start from a random "spawn point".
**** I believe most FPS games make you lose all upgrades, but this is not an option in Vega Strike, or things will get boring quickly.
**** How do games like Ultima or WoW behave when you die? Do you lose everything (obviously you can't lose all your experience)?
***** Diablo II: A dead body is left at the place where you died. With it are all your equipment, upgrades and the gold (credits) you carried. Your team members can recover all that for you or you can hurry there yourself. Some of the gold is alsways lost however. In more difficult settings (hell and nightmare) also some of your experience is lost. ([[User:Zeog|Zeog]] 01:24, 4 July 2006 (PDT))
***** WoW: Your equipment takes some damage. With high-end gear, this costs enough that death is worth avoiding. (top-level characters don't have to worry about the XP loss). There's also the time it takes to run your ghost to your corpse. If you just log off without recovering your corpse, I think your gear takes more damage. In Vega Strike, you could lose some of your cargo, and take some damage to your upgrades.
***** I think that something more realistic will do, a ship has an eject option, we could say that auto eject works when the ship blows up, since credit should be theoraticlly in a bank account it doesnt get stolen, but all equipment is lost, about stronger richer players having lots of cash and a serious ship would need to avoid death or else they would have to buy a ship that is a lot worse, and people that cannot afford a ship could join a faction doing missions for it as a pilot and buying a ship when they get enough cash.

[[Category:Development]]

Development:Network

2014-04-26T15:05:02Z

Ezee: mooved on todo

Development:Network

2014-04-26T15:00:31Z

Ezee: /* NEW : DATABASE FOR ACCOUNT SERVER */

Development:Network

2014-04-26T15:00:04Z

Ezee: /* Markets: */

Development:Network

2014-04-26T14:58:04Z

Ezee: update

Development:Network

2014-04-26T14:26:41Z

Ezee: update 2014 for MMO side

Development:Network:Testing

2014-04-20T01:02:14Z

Ezee: fix of bad link

=Compilation=
Every should compile without a hitch. If it does not, post a question on the forum about the specific error.
==Linux==
The regular Makefile can compile '''vegaserver''' and '''accountserver''' in Linux.
==Windows==
There should be two projects for vegaserver and accountserver. They ''should'' compile without any changes.

I also recommend that you build vegastrike using "Debug GLUT" or "Release GLUT", since you will get a console. Otherwise you only get a stderr/out.txt for one of the clients.
=Setup=
* You will want to move the '''vegastrike.config.netplayer''' file over the '''vegastrike.config''' file to get some extra settings.
* Now, open up Setup.
** You should be able to choose between players (test1, test2, and test3).
** You should also get an option for screen resolution labeled "Skinny". This will make a skinny windows so that you can fit two on top of each other. At 1600x1200 you can fit two instances of VS, as well as three terminals and a setup screen if you tile it right.
=Starting=
==Linux==
I highly recommend running linux programs in separate '''GNU screen''' windows. If you have never used screen before, it's basically a detachable session that holds multiple "terminals". You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
* You will want to run everything from the ''data'' directory.
* First, start up the accountserver: '''../vegastrike/accountserver'''
* Now, start up vegaserver: '''../vegastrike/vegaserver'''
* Clients should be able to connect. I have only tested localhost, but remote connections ''should'' be able to connect as well with some config file changes.
** To connect, run vegastrike with the --net option: '''../vegastrike/vegastrike --net'''
** To run more than one client, you must choose a different user, so select test2 for example, run vegastrike, then select test1 and run vegastrike again in a different terminal.
*** Note that as soon as the window appears, the config file has finished being read, so you can change settings like the username without any side effects.

==Windows==
* Double-click '''accountserver.exe'''
* Double-click '''vegaserver.exe'''
* Now, click on either '''debug_net_client.bat''' or '''release_net_client.bat''', depending on whether you built in "Debug GLUT" or "Release GLUT".
* To open more than one, switch users and try again.
** Note that as soon as the window appears, you can change settings like the username in setup for the second client without any side effects on the loading one.
* You should get a console for each client as well as the servers.

=Loading and Playing=
* When the window opens up, the network will start connecting when the screen reads "Vegastrike Loading..."
* You will very possibly encounter the client exiting on load. Read the console for more info. A common error is LOGIN_ALREADY, meaning that the client was already connected, or that there was another error and the accountserver didn't reset itself. This will hopefully be fixed someday.
* If you get passed the "Vegastrike Loading..." screen then everything should continue as normal until you get into space. You should not see anyone else at first...
* If you connect with another client and a different username, the second client should target the first client, however the first client will not autotarget, so hit "t" to target the new unit.
* Fly around in both users and fire around and so on. However beware: As soon as one client dies from a collision, the server will crash due to a NULL pointer dereference. This is being looked at, but until it is fixed, don't die by crashing into someone.

=Playing with the Sourceforge Account Server=
This should work in most situations and is easier than running your own accountserver.

*Register an account with [http://vegastrike.sourceforge.net/cgi-bin/register.py register.py] using your forums login. See [http://forums.vega-strike.org/viewtopic.php?t=7355 this thread] for more info.

*Compile vegaserver.

*Edit the "accountsrv" entry in vegaserver.config so it reads:
:<pre><var name="accountsrv" value="http://vegastrike.sourceforge.net/cgi-bin/accountserver.py"/></pre>
:(Unless you want to run under a 'mod' by appending ?modname to the URL, in which case you have to register under one as well by doing the same to [http://vegastrike.sourceforge.net/cgi-bin/register.py register.py]. Currently, I think 'test' is the only mod.)

*You can use part or all of the config it generates for you, but make sure you get the account and network settings. Make sure that server_ip is set to "127.0.0.1" (localhost) if you want to play on your own vegaserver. If a second player wants to connect to your machine and it is configured as a server (with an external IP, or behind a NAT set up with port forwarding), have them put your IP address in this field.

*Start vegaserver on the host machine. It should connect to the accountserver running on sourceforge.net, although it's possible to compile and run your own (I haven't tried this successfully yet.)

*Start up your clients like so:
:<pre>vegastrike --net</pre>
If all goes well, that should work!

=See also=
*[http://forums.vega-strike.org//viewtopic.php?t=5225 Networking code testing and development thread]

Development:Network:Testing

2014-04-20T01:00:09Z

Ezee: fix of bad link

=Compilation=
Every should compile without a hitch. If it does not, post a question on the forum about the specific error.
==Linux==
The regular Makefile can compile '''vegaserver''' and '''accountserver''' in Linux.
==Windows==
There should be two projects for vegaserver and accountserver. They ''should'' compile without any changes.

I also recommend that you build vegastrike using "Debug GLUT" or "Release GLUT", since you will get a console. Otherwise you only get a stderr/out.txt for one of the clients.
=Setup=
* You will want to move the '''vegastrike.config.netplayer''' file over the '''vegastrike.config''' file to get some extra settings.
* Now, open up Setup.
** You should be able to choose between players (test1, test2, and test3).
** You should also get an option for screen resolution labeled "Skinny". This will make a skinny windows so that you can fit two on top of each other. At 1600x1200 you can fit two instances of VS, as well as three terminals and a setup screen if you tile it right.
=Starting=
==Linux==
I highly recommend running linux programs in separate '''GNU screen''' windows. If you have never used screen before, it's basically a detachable session that holds multiple "terminals". You can switch between them with '''C-a "''' and you can make new ones with '''C-a c''' -- you can detach with '''C-a d''' and reattach with '''screen -r'''... Very handy for running multiple instances of Vegastrike in my opinion, but don't use it if you are not comfortable as it can be confusing.
* You will want to run everything from the ''data'' directory.
* First, start up the accountserver: '''../vegastrike/accountserver'''
* Now, start up vegaserver: '''../vegastrike/vegaserver'''
* Clients should be able to connect. I have only tested localhost, but remote connections ''should'' be able to connect as well with some config file changes.
** To connect, run vegastrike with the --net option: '''../vegastrike/vegastrike --net'''
** To run more than one client, you must choose a different user, so select test2 for example, run vegastrike, then select test1 and run vegastrike again in a different terminal.
*** Note that as soon as the window appears, the config file has finished being read, so you can change settings like the username without any side effects.

==Windows==
* Double-click '''accountserver.exe'''
* Double-click '''vegaserver.exe'''
* Now, click on either '''debug_net_client.bat''' or '''release_net_client.bat''', depending on whether you built in "Debug GLUT" or "Release GLUT".
* To open more than one, switch users and try again.
** Note that as soon as the window appears, you can change settings like the username in setup for the second client without any side effects on the loading one.
* You should get a console for each client as well as the servers.

=Loading and Playing=
* When the window opens up, the network will start connecting when the screen reads "Vegastrike Loading..."
* You will very possibly encounter the client exiting on load. Read the console for more info. A common error is LOGIN_ALREADY, meaning that the client was already connected, or that there was another error and the accountserver didn't reset itself. This will hopefully be fixed someday.
* If you get passed the "Vegastrike Loading..." screen then everything should continue as normal until you get into space. You should not see anyone else at first...
* If you connect with another client and a different username, the second client should target the first client, however the first client will not autotarget, so hit "t" to target the new unit.
* Fly around in both users and fire around and so on. However beware: As soon as one client dies from a collision, the server will crash due to a NULL pointer dereference. This is being looked at, but until it is fixed, don't die by crashing into someone.

=Playing with the Sourceforge Account Server=
This should work in most situations and is easier than running your own accountserver.

*Register an account with [http://vegastrike.sourceforge.net/cgi-bin/register.py register.py] using your forums login. See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7355 this thread] for more info.

*Compile vegaserver.

*Edit the "accountsrv" entry in vegaserver.config so it reads:
:<pre><var name="accountsrv" value="http://vegastrike.sourceforge.net/cgi-bin/accountserver.py"/></pre>
:(Unless you want to run under a 'mod' by appending ?modname to the URL, in which case you have to register under one as well by doing the same to [http://vegastrike.sourceforge.net/cgi-bin/register.py register.py]. Currently, I think 'test' is the only mod.)

*You can use part or all of the config it generates for you, but make sure you get the account and network settings. Make sure that server_ip is set to "127.0.0.1" (localhost) if you want to play on your own vegaserver. If a second player wants to connect to your machine and it is configured as a server (with an external IP, or behind a NAT set up with port forwarding), have them put your IP address in this field.

*Start vegaserver on the host machine. It should connect to the accountserver running on sourceforge.net, although it's possible to compile and run your own (I haven't tried this successfully yet.)

*Start up your clients like so:
:<pre>vegastrike --net</pre>
If all goes well, that should work!

=See also=
*[http://forums.vega-strike.org//viewtopic.php?t=5225 Networking code testing and development thread]

Development:Scripts & Tools

2014-03-27T16:11:29Z

Ezee: fixed bad forum link

{{parent_link|
|parent=[[Development]]
}}
----

= Introduction =
These handy scripts and tools are here to make your life easier.
Please note that the official standard for support tools is:
* C++, or
* Python using [http://wiki.python.org/moin/TkInter Tkinter]

{| style="width: 100%; text-align: center; background-color:#9090FF" cellpadding="2" cellspacing="1"
|-style="background-color:#606060;"
! Tool !! Author !! License !! Platforms !! Engine version !! Features !! User Manual
|-valign="top" style="background-color:#909090;"


|-style="background-color:#9090FF;"
| Mesher
| klauss
| GPL || Posix, Win || -
| CLI converter obj <-> bfxm <-> xmesh
| [[HowTo:Add_Ships|Mesher HowTo]]
|-


|-style="background-color:#9090FF;"
| [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=11885 UnitConverter OBJ->BFXM]
| [[User:pyramid|pyramid]]
| GPL || all with Python 2.5 || -
| * convert obj to bfxm *add and compress textures * edit unit info
| [[Development:Tools:UnitConverter|UnitConverter User Manual]]
|-


| CampaignEditor
| Daniel Aleksandrow
| GPL || all with Java SE 6 || -
| create and edit campaigns
| -

|}

= Internal tools =
Tools developed for Vega Strike
* Mesher utility: Converts from/to Wavefront .obj+.mtl, xmesh(es), and BFXM file formats.
* ucsv.py: (Python) Conversion script for turning .xunit files into rows in units.csv format
* 3ds2xml: (Perl) script for converting .3ds files into .xmesh format. Doesn't appear to do axis translation properly, known to be somewhat flaky.
*[WIP] [[Development:Script:obj2obj converter|obj2obj converter]] (Perl, commandline) - Converts obj files to cockpit files. or extracts tag-data from the models. (''At least that's what is planned, Testing under Win32/Linux. [[User:pontiac|Pontiac]]'')
* Configuration Parser (file: objconv/configparser.py in vegastrike CVS, Python) - Goes through the source tree and produces a config file (pygrep.config at present) containing every variable *used* in game, every possible command to bind to keys, and every colour definition that can be specified. Still under development.
*[WIP] OBJ to Vega Strike cockpit converter ([http://vegastrike.sourceforge.net/users/pontiac/scripts/obj2vs_cockpit_obj/ obj2vs_cockpit_obj], Perl)

= External tools =
Plugins and scripts for external programs
*[http://members.chello.at/stefbuer/vegastrike.html XMESH import/export plugin for Wings3D]
*[http://www.talisiorder.ca/template.php?T=Vegastrike%20Addons&P=vegastrike/vegastrike.html XMESH converter for lightwave]
*[WIP] [http://www.geocities.com/cubofjudahslion/VS/xmesh.zip XMESH import script for Blender]

* [http://registry.gimp.org/node/70 DDS plugin for the GIMP]
* [http://en.wikipedia.org/wiki/IrfanView Irfanview] (freeware for Windows) supports the DDS image file format.
* [http://en.wikipedia.org/wiki/Kde KDE]'s image libraries (version >= 3.3.0) support reading the DDS file format, so e.g. gwenview, kview and konqueror can view texture files.
* See [[Development:Orbital_Planet_Surfaces]] for info on NVidia's DDS compressor software.

= See also =
* [[OOG_Tools|Out-Of-Game Player Tools]]
* [http://forums.vega-strike.org//viewtopic.php?t=2902 List of VS object conversion scripts and tools] forums thread

[[Category:Development]]

Development:Base Backgrounds

2014-03-22T01:02:49Z

Ezee: fixed bad link "Switching a GUI"

{{parent_link|parent=[[Development]]}}
----
=Introduction=

This page summarizes concepts and approaches recommended to add base or planet backgrounds to Vega Strike.

=Development Needs and Tasks=

We could always use more backgrounds. Ideally, each planet and base in Vega Strike would have a unique background.

Please head over here for a list of open tasks: [[Development:2D_Images#Base_Backgrounds]]

=Docking Backgrounds=

==Texture Requirements==

===Generic Image Requirements===

Please read this [[Development:Graphics_Requirements]] page before continuing to the specific requirements.

===Specific Image Requirements===
That leaves few options:
*1024x1024
*2048x2048

Keeping original high resolution image (e.g. 8192x or 4096x) versions in stock helps maintaining quality and scalability as game development progresses or typical screen resolutions rise in the future with better hardware available to the players.

==Creating and Naming==

===Comments by MamiyaOtaru in Forums===

First off, the bases are not full screen due to the config file, not the sprite file. Change that first to have fullscreen bases. So, the explanation:

In the coordinate system, 0,0 is at the center not the top left. The coordinate system is cartesian, left to right is -1 to 1 x, top to bottom is 1 to -1 y.

Width 2 means the width of the screen (two halves, from -1 to 1) and height 2 means the height of the screen.

In your example, the image is meant to take up 3.104/2 screen widths and 2.4832/2 screen heights. This is because the actual used part of the image (320x200) is approx 512*(2/3.2) x 256*(2/2.5). 3.104 and 2.4832 stretch the image beyond fullscreen, so that the part of the image that actually has something in it (which is only 320x200) will take up fullscreen.

The next two numbers are where the image is centered. Often, those two numbers are actually stored elsewhere. In cockpits, they are stored in the .cpt file and only the dimensions are actually in the .spr file. Here, the X and Y coordinates for the center of the image are in /bases/*.py. Your example is in /bases/pleasure_land.py

Your example is therefore actually
3.104 2.4832 width and height
and
0.582 -0.2716 centerX and centerY

The center of the image is thus a little more than half the distance from the center of the screen to the right hand side of the screen. This serves to place the center of the area that has actual content at the center of the screen. The center is a bit more than a quarter of the way from the center to the bottom of the screen for the same reason.

If you use an image that fills up the whole bitmap, without empty space like the priv remake backgrounds, to go fullscreen you would use something like this
2 2 (2 half widths and half heights, from -1, -1 to 1, 1)
0 0 (centered in the center of the screen)

Oh, and pleasure_land.py is also where the animations are linked, if you'd like to remove them for a different background. The animations are the water and the building lights: Jolson_LandingBay_wtr and Jolson_LandingBay_blt respectively. Remove their lines.

===Python Scripts===

You will need to create the appropriate python scripts to be placed in the <code>bases</code> directory.

Each planet has a script labeled according to its texture name (i.e. texturename_day.py, texturename_night.py, texturename_sunset.py, etc.) What this means is that each planet you want specific control over will require its own texture. Not too big a task (as I assume the number of planets for which this control is needed is not major), as you can almost just copy and paste the old python files for the planet type, but you will also need to edit units.csv to add that planet type. This is easy if you know what you're doing, but obviously is not a long term solution to such a problem. (If anyone knows of a better way that we can do this, let me know!)

Each unit type has a script labeled according to its unit and faction name (unitname_factionname.py, or ignoring factions unitname.py). Here the trick will be to create a python file that checks the name of the unit you are docked to to see if it's the campaign one. If it is then do something special, else do the same as every other unit.

Basically, these scripts are simply run when the player docks. We can't force a different script to load at will, only make sure that the script VS looks for contains what we want it to. However, it might be useful in future to change this...

'''Room definition'''

<code><pre>room1 = Base.Room ('Aera Planet')
Base.Texture (room1, 'tex', 'bases/generic/aera_planet.spr', 0, 0)</pre></code>

In the first line, you assign the room object type to your script variable giving the unique argument, the name that will be visible on the in-game interface.
The second line defines the texture image sprite for the base background with the argument list ''roomvariable'', ''linkname'', ''spriteaddress'', ''centerx'', ''centery''.

'''Ship placement'''

<code><pre>Base.Ship (room1, 'ship', (-0.3, -0.3, 6), (0, 0.93, -0.34), (-1, 0, 0))</pre></code>

The above code defines the placement for the ship in room1, assuming room1 is the landing pad room or the repairs and upgrades room, where the player's ship should show. It has the form:
Base.Ship (''roomvariable'', ''linkname'', ''vectorP'', ''vectorR'', ''vectorQ'')

where:
* ''roomvariable'' - the room in which you place the button
* ''linkname'' - arbitrary name to make your code readable
* ''vectorP'' - position of the ship with (''centerx'', ''centery'', ''scale'') -- Note that scale is a Z coordinate in perspective, so you must adjust your X and Y accordingly as it gets farther away.
* ''vectorR'' - ship up orientation with up-vector coordinates (''x'', ''y'', ''z'')
* ''vectorQ'' - ship nose orientation with forward-vector coordinates (''x'', ''y'', ''z'')

'''''Testimonial by chuck_starchaser'''''

''Adjusting these vectors (particularly the up and forward) manually, by trial and error, can be very time consuming and tedious. The sum of the squares of the x, y and z values in the up and forward vectors must add to one. In other words, the vectors should be "normalized", or of "unit-length". Also, the up and forward vectors should be normal (perpendicular) to one another. In arithmetic terms, their dot product should be zero. And what's the dot-product? The result of multiplying up.x times forward.x, adding to that the product of up.y times forward.y, and adding to that the product of up.z times forward.z. That should be zero if the two vectors are perpendicular. Yes; it's Hell; been there and survived. But there's an escape... maybe...''

''If you have a background artwork with a given perspective of the landing pad, say, you may want to load it into Blender as a background image. Set your view to orthogonal, with positive x to the right, and positive y up on the screen. Place a cube. Scale it so it's 2 x 2 x 2 size. Go to perspective, transparent mode (Numpad 5, Z in Blender). Set your view so that the cube extends over the screen, half visible, half beyond the screen borders. Now, load the mesh of a typical ship that you'd have land there. Do NOT change your view; but rotate the ship's mesh to get the perspective of it you want, over the picture. Now you can snap your cursor to the center of the ship (Shift-S, Cursor to selection, in Object mode) and read the cursor's position from the View Properties screen. That's NOT the values you want for the P vector, but save them for now. For the forward vector, in edit mode, select the nose vertex for the ship, snap cursor, write down the xyz. Subtract the xyz for the ship's center. Normalize it (i.e.: divide all three numbers by the square root of the sum of the squares. That's your vectorQ. For the UP vector, find any two vertices on the ship that are vertically aligned, get their coords, subtract, normalize.''

''VectorP will be a bit trickier: You need to measure the position of the center of the ship on-screen, placing a ruler on your monitor, careful not to scratch it. And you need to translate those measurements to VS screen coordinates, where the far left is -1 X, far right is +1 X, top is +1 Y, bottom is -1 Y. The two numbers you obtained are centerx and centery, but what should scale be? Frankly, I (chuck starchaser) don't know how scale works; I just adjusted it for PU by trial and error.''

''Hope this helps. The idea for this Blender method came to me in retrospect, today (May 23, 2008), and I haven't actually tested it. Be sure to edit this document to fix it as necessary, if you do make it work; or if you come up with a better method.''

'''Button definition'''

<code><pre>Base.Comp (room1, 'CargoComputer', 0.289063, -0.283854, 0.146484, 0.179688, 'Cargo Computer', 'Cargo')
Base.Link (room1, 'goto_exterior', 0.3, -0.3, 0.5, 0.3, 'Planet Exterior', room2)</pre></code>

The above code defines the button for the cargo computer and a link button to an exterior background image with the following convention:
Base.''Object'' (''roomvariable'', ''linkname'', ''leftx'', ''bottomy'', ''width'', ''height'', ''displaytext'', ''linkobject'' )

where:
* ''roomvariable'' - the room in which you place the button
* ''linkname'' - arbitrary name to make your code readable
* ''leftx'', ''bottomy'' - button left bottom corner coordinates; ranging from -1 on the left to 1 on the right, -1 on bottom 1 on the top
* ''width'', ''height'' - button size; full screen size is 2, half screen is 1.
* ''displaytext'' - the text that will be shown in game
* ''linkobject'' - the variable name of the object in your python script or a name predefined in the engine

In addition, for Base.Comp, the ''linkobject'' is used to determine the services available at that particular computer:
* Cargo
* Missions
* News
* Info
* Upgrade
* ShipDealer

==Including and Testing==

You'll need to create a sprite file referencing the image. See more information on how to do this in [[HowTo:Edit_HUDs|HowTo:Edit HUDs]]

==Selection and Vetting==

===Some Thoughts===

Once you have chosen a replacement candidate and have one or more proposals...

===The Process===
If you are not sure that your texture meets the basic requirements, then please open a forum topic posting your textures.
Please verify the summary of requirements [[#Including_and_Testing|above]].

If a texture that you have created meets the texture requirements, then:
* Open a poll for a reasonable period of time (e.g. 2 weeks) and describe:
** which texture(s) you'd like to replace
** display your candidates
** briefly describe the method of creation and tools used
** If you'd like to replace more than one texture, describe how you would assign the favorites of the poll to the individual textures

* After a set period of time
** announce the winners
** and call the poll closed

* Then
** Submit the textures to svn (in case you have commit rights attributed), or
** through the forum ask a developer with write access to submit them (e.g. the maintainer of this page, [[User:pyramid|pyramid]]).

==Submission==

AKA: Committing to SVN.

=References=

==Software, Tools==
For a comprehensive list of tools, please see:
*[[Links:Graphic_Applications|Links:Graphic Applications]]
*[[Links:3D_Applications|Links:3D Applications]]

==See Also==
* See the following forum discussions
** [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=6734 Base Backgrounds]
** [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7600 Generic Spaceport Backgrounds]
** [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9093 Planet background]
** [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=2292 How to change the base art in a planet]
** [http://forums.vega-strike.org//viewtopic.php?t=13255 Switching a GUI ]
** other discussions: [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4636], [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1679&start=0&postdays=0&postorder=asc]
* Example Scripts

'''Author: [[User:pyramid|pyramid]]'''

[[Category:Development]]

Fr:Development:Translations:ArboTravailFr

2014-03-17T18:44:02Z

Ezee: update avancement quests

= Mise en place =
Un nouveau repository a été créé sur github https://github.com/costalfy/Vega-Strike contenant le repertoire data du trunk de sourceforge en date du 13/04/2014 (r13675)
J'ai été obligé de supprimer les fichiers suivant pour éviter de faire exploser mon quota :
* *.bmp
* *.psd
* *.jpg
* *.png
* *.ogg
* *.texture
* *.image
* *.bfxm
* /textures

J'ai créé un nouveau repertoire i18n/LC_MESSAGES qui contiendra les fichiers à traduire 
Quelques indications pour l'utilisation du dépôt Vega Strike sous Github ici : [[Development:Translation:FrenchWorkTree:Github |Github]]

= Procédure =
Merci de prendre connaissance de la manière de [[Development:Translation:FrenchWorkTree:Github|travailler avec github]] ainsi que [[Development:Translations:FrenchWorkTree:Notes|les remarques sur ce qui est à traduire]] dans le code source
== Ajouter la balise gettext dans le code source ==
Ajouter l'internationalisation dans le code python ou c++ est assez simple à réaliser.
Il faut scanner le code source et repérer le texte anglais hardcodé. Ensuite, pour chaque texte, il faut l'enrober de la balise gettext '''_(...)''' comme ceci :

Base.Message("No? Come back to me again if you change your mind.")
devient :
Base.Message(_("No? Come back to me again if you change your mind."))

un exemple est déjà visible sur le repository https://github.com/costalfy/Vega-Strike/commit/9cf2078c3fc39681404e59512b2a86503b49f887

[[Development:Translations:FrenchWorkTree:Notes | Notes sur les textes traduisibles ou non par type de fichier]]

== Générer le .po depuis le code source avec PoEdit ==
Lorsque tout le code source aura été scanné, on utilisera le logiciel [http://www.poedit.net/ PoEdit] pour scanner le code source et repérer toutes les balises _(...) qu'on aura ajouté.
Le logiciel créera le fichier vegastrike-fr_FR.po qui contiendra l'extration de tout le texte à traduire... magique :)

== Traduire le .po avec PoEdit ==
Les traducteurs utiliseront le meme logiciel pour ouvrir le fichier /data/i18n/LC_MESSAGES/vegastrike-fr_FR.po et devront traduire chaque ligne une par une... ça c'est moins magique ;-)

= Etat d'avancement =
Ajouter l'arboresence qui a été traitée. si tout un répertoire est traité inutile d'indiquer la liste de tous les fichiers, juste un (*) à coté du répertoire suffira ;-)
data
|---modules
| |-------- quests (*) ( ezee )
|---bases
| |---fixers
| | |---no.py
| |---bartender.py
| |---computer_lib.py (en cours, GreenD)
| |---mission (*) j'ai du refactorer tous les .mission pour que poedit puisse détecter le texte a traduire

Fr:Development:Translations:ArboTravailFr

2014-03-13T18:10:46Z

Ezee: correction mineure de conjugaison

= Mise en place =
Un nouveau repository a été créé sur github https://github.com/costalfy/Vega-Strike contenant le repertoire data du trunk de sourceforge en date du 13/04/2014 (r13675)
J'ai été obligé de supprimer les fichiers suivant pour éviter de faire exploser mon quota :
* *.bmp
* *.psd
* *.jpg
* *.png
* *.ogg
* *.texture
* *.image
* *.bfxm
* /textures

J'ai créé un nouveau repertoire i18n/LC_MESSAGES qui contiendra les fichiers à traduire

= Procédure =
== Ajouter la balise gettext dans le code source ==
Ajouter l'internationalisation dans le code python ou c++ est assez simple à réaliser.
Il faut scanner le code source et repérer le texte anglais hardcodé. Ensuite, pour chaque texte, il faut l'enrober de la balise gettext '''_(...)''' comme ceci :

Base.Message("No? Come back to me again if you change your mind.")
devient :
Base.Message(_("No? Come back to me again if you change your mind."))

un exemple est déjà visible sur le repository https://github.com/costalfy/Vega-Strike/commit/9cf2078c3fc39681404e59512b2a86503b49f887

== Générer le .po depuis le code source avec PoEdit ==
Lorsque tout le code source aura été scanné, on utilisera le logiciel [http://www.poedit.net/ PoEdit] pour scanner le code source et repérer toutes les balises _(...) qu'on aura ajouté.
Le logiciel créera le fichier vegastrike-fr_FR.po qui contiendra l'extration de tout le texte à traduire... magique :)

== Traduire le .po avec PoEdit ==
Les traducteurs utiliseront le meme logiciel pour ouvrir le fichier /data/i18n/LC_MESSAGES/vegastrike-fr_FR.po et devront traduire chaque ligne une par une... ça c'est moins magique ;-)

= Etat d'avancement =
Ajouter l'arboresence qui a été traitée. si tout un répertoir est traité inutile d'indiquer la liste de tous les fichiers, juste un (*) a coté du répertoire suffira ;-)
data
|---bases
| |---fixers
| | |---no.py
| |---bartender.py

HowTo:VCPP Compiling

2014-02-24T03:22:07Z

Ezee: update bug GL_TEXTURE_CUBE_MAP_SEAMLESS 0x884F

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*4_Create a folder trunk\vega-vc9
*5_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

*5-There will be errors if you try to compile , caused by Boost 1.45 .
( version 0.5.2 of vegastrike contain only boost 1.53 )
So checkout also the Boost 1.45 in the same folder than the 1.53 ( in vegastrike/Boost )
http://svn.code.sf.net/p/vegastrike/code/branches/vegastrike_0_5_1/vegastrike/boost/1_45

*6-There is bug with a #define and GL_TEXTURE_CUBE_MAP_SEAMLESS
Solution is [http://forums.vega-strike.org/viewtopic.php?f=5&t=18590&p=135450#p135450 in the forum ]

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-24T03:13:23Z

Ezee: update version of boost 1.45

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*4_Create a folder trunk\vega-vc9
*5_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

*5-There will be errors if you try to compile , caused by Boost 1.45 .
( version 0.5.2 of vegastrike contain only boost 1.53 )
So checkout also the Boost 1.45 in the same folder than the 1.53 ( in vegastrike/Boost )
http://svn.code.sf.net/p/vegastrike/code/branches/vegastrike_0_5_1/vegastrike/boost/1_45

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-24T02:18:14Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*4_Create a folder trunk\vega-vc9
*5_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

There will be errors if you try to compile , caused by a wrong path to Boost 1.45 .

So go to Project->properties->C/C++ -> general

Add the include path to Boost 1.53 ( mine is ..\trunk\vegastrike\boost\1_53 )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-24T02:15:36Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*4_Create a folder trunk\vega-vc9
*5_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

There will be errors if you try to compile , caused by a wrong path to Boost 1.45 .

So go to Project->properties->C/C++ -> general

Add the path to Boost 1.53 ( in your folder vegastrike )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-24T02:07:45Z

Ezee: update vc9

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*4_Create a folder trunk\vega-vc9
*5_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-24T02:03:09Z

Ezee: Undo revision 19707 by Ezee (talk)

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\vega-vc9
*43_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-24T01:58:02Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\vega-vc9
*4_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-24T01:57:22Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\vega-vc9
*43_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

DEPENDENCIES FOR VISUAL STUDIO ( WIndows )

2014-02-23T23:05:04Z

Ezee: update to 0.5.2 state

Here we need to talk about all libs used in a Vega Strike project under windows .

== VS 0.5.2 dependencies :==

----

{{FIXME}} ( todo list all the dependencies )

*DATA
needed to run the .exe :

http://svn.code.sf.net/p/vegastrike/code/trunk/data
Copy the content in yourLocalProject/Win32/Bin/Modules

*PYTHON 2.7
The correct python package for vc9 is included in :

http://svn.code.sf.net/p/vegastrike/code/trunk/data
Must be unzipped in yourLocalProject/Win32/Bin/Modules

HowTo:VCPP Compiling

2014-02-23T08:02:38Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I had a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*3_Create a folder trunk\vega-vc9
*3_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-22T19:44:21Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

*Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I add a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*3_Create a folder trunk\vega-vc9
*3_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-22T19:43:54Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I add a lot of troubles to compile , link and run the program !

So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN

( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*3_Create a folder trunk\vega-vc9
*3_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-22T19:42:50Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I add a lot of troubles to compile , link and run the program !
So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN
( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*3_Create a folder trunk\vega-vc9
*3_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default .

( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-22T19:42:19Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I add a lot of troubles to compile , link and run the program !
So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN
( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*3_Create a folder trunk\vega-vc9
*3_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default . ( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "

( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-22T19:40:56Z

Ezee: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I add a lot of troubles to compile , link and run the program !
So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN
( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*3_Create a folder trunk\vega-vc9
*3_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default . ( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "
( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:VCPP Compiling

2014-02-22T19:39:27Z

Ezee: /* UPDATE Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-vc</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-vc9</code> for all Visual C++ editions, <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.</strike>

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 11.x (Visual Studio Express 2012)==

{{Fixme}} Write Me - Until specific instructions are written by someone knowledgeable, follow information for previous versions and supplement it with up to date information about compiling from the forums.

==Visual C++ 10.0 (2010 Express)==

{{Fixme}}Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual Studio Express].
If you encounter any issues post a new topic in the [http://forums.vega-strike.org/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. Run the installer, uncheck all the boxes on each page if you want a lighter download. It will do everything on it's own then ask to reboot.
# To update for Python 2.7 you will need to download the latest 2.7 source release: [http://www.python.org/download/ Download latest source Python 2.7]
or directly [http://www.python.org/download/releases/2.7.6// www.python.org/download/releases/2.7.6]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

Update --[[User:Ezee|Ezee]] 19:39, 22 February 2014 (UTC)

I add a lot of troubles to compile , link and run the program !
So this is how to obtain a working version of Vegastrike 0.5.2 from the SVN
( with turtoise )

YOU MUST CREATE FIRST THE EMPTY FOLDERS IN YOUR COMPUTER :

The idea is to recreate the tree of the svn .

*1_Create a folder trunk
*2_Create a folder trunk\win32
*3_Create a folder trunk\data
*3_Create a folder trunk\vega-vc9
*3_Create a folder trunk\vegastrike

from there , you are ready to check out the SVN .

*1- Select your folder vega-vc9
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/vega-vc9

*2- Select your folder vegastrike
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/cod/trunk/vegastrike

*3- Select your folder data
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/data

*4- Select your folder win32
Right-click and use tortoise -> checkout with :
http://svn.code.sf.net/p/vegastrike/code/trunk/win32

Now your solution vc9 should be ok .
BUT THE .EXE WILL BE BUILD IN "\trunk\vega-vc9\Release" or "\trunk\vega-vc9\Debug"
by default . ( you won't be able to run or debug the game , step into etc ... )

So now , go to your project options , in " Linker" , change the output path like this :
" D:\program\trunk\win32\bin\$(ProjectName).exe "
( change D:\program\trunk\ by your path :wink: )

Almost ended .

You need to copy the content of your folder "data" in your folder win32\bin
DON'T FORGET TO UNZIP THE PYTHON 2.7 rar in \win32\bin !

GOOD !
Enjoy your new Vegastrike programming environment !

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://forums.vega-strike.org/ forum] or specifically on [http://forums.vega-strike.org/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI (deprecated)===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

VSOGRE DOCUMENTATION

2014-02-20T14:47:29Z

Ezee: Created page with "This is the Doxygen c++ documentation for the experimental branch of Vegastrike , VSOgre . [http://spacetechs.free.fr/VEGASTRIKEDEV/DOC/VSOGRE/html/namespace_v_s_ogre.html VSOgr..."

This is the Doxygen c++ documentation for the experimental branch of Vegastrike , VSOgre .

[http://spacetechs.free.fr/VEGASTRIKEDEV/DOC/VSOGRE/html/namespace_v_s_ogre.html VSOgre doc]

DOCs

2014-02-20T14:44:40Z

Ezee: VSOGRE DOCUMENTATION - Experimental ogre3d port documentation, in .html format

NPC

2014-02-19T19:41:25Z

Ezee: /* INFLUENCES IN THE GAMEPLAY */

'''NPC''' , '''N'''on '''P'''layable '''C'''haracters in Vega Strike {{Fixme}}

Let's see who are the NPC in our vegastrike universe !

And how they influence the Gameplay ( fight , economy , quests , communications )

== NPC INFLUENCE IN VEGASTRIKE 0.5.1 ==

ToDO :
*List the actual pros and cons , give links to forum threads .
*Give some scripts exerpts .
*Propose ideas for future NPC dev

== ACTUAL PROS AND CONS ==

ToDO !

== INFLUENCES IN THE GAMEPLAY ==

ToDO ( next section describe it well in the near future )

== DEV CONCEPTS ==

<blockquote>
Thinking some more on basic categories for NPCs, there are

*Universe level: noteworthy characters in the VS universe you might have some reason to interact with (heads of state, famous terrorists, individuals who played/will play key roles in previous/later events or events otherwise outside of player control, etc.)
...
...
*Time-period specific NPCs: Potentially non-specific people occupying particular positions of interest, and a hodgepodge of assorted flavor characters to give the universe a lived-in feeling and different parts of it different flavors. These people may offer specific types of quests, but not specific quests, and may not have any non-dialog interactions at all. They'll be around whatever path you take, and won't influence your particular path. Not high-priority. Examples: Unique bar patrons, traveling merchants (that actually travel), some minor regional military commanders, uncommon fixers, travelling fixers, minor celebrities (that you can kill off or allow to die, etc. without screwing up the future history). Good subjects for news-stories.
...
...
*Generic NPCs: Interchangeable fixers, bar patrons, random inhabitants, bartenders, etc. Examples: Bounty fixer, Patrol fixer, Merchant Fixer
...
...
*Ephemeral campaign NPCs: Specific individuals pertaining to a quest that exist (practically speaking) only for the duration of the quest. Before the quest, they don't appear. After the quest they don't appear. Example: Red-shirt wingman provided by mission-giver as assistant. Might have interesting dialog and distinct personality. Probably has a name. Might even not get blown up, but you're never going to see that NPC outside of the context of the particular quest or quest-line.

*Persistent campaign NPCs: NPCs whose persistent residence in the universe must be taken into account. You might only be able to interact with them in limited ways outside of particular quest lines, but their presence in the game universe persists in some palpable ways outside of the quest line itself.

''From ' jacks ' in ' Dramatis Personae .''</blockquote>

NPC

2014-02-19T19:40:27Z

Ezee: /* ACTUAL PROS AND CONS */

'''NPC''' , '''N'''on '''P'''layable '''C'''haracters in Vega Strike {{Fixme}}

Let's see who are the NPC in our vegastrike universe !

And how they influence the Gameplay ( fight , economy , quests , communications )

== NPC INFLUENCE IN VEGASTRIKE 0.5.1 ==

ToDO :
*List the actual pros and cons , give links to forum threads .
*Give some scripts exerpts .
*Propose ideas for future NPC dev

== ACTUAL PROS AND CONS ==

ToDO !

== INFLUENCES IN THE GAMEPLAY ==

== DEV CONCEPTS ==

<blockquote>
Thinking some more on basic categories for NPCs, there are

*Universe level: noteworthy characters in the VS universe you might have some reason to interact with (heads of state, famous terrorists, individuals who played/will play key roles in previous/later events or events otherwise outside of player control, etc.)
...
...
*Time-period specific NPCs: Potentially non-specific people occupying particular positions of interest, and a hodgepodge of assorted flavor characters to give the universe a lived-in feeling and different parts of it different flavors. These people may offer specific types of quests, but not specific quests, and may not have any non-dialog interactions at all. They'll be around whatever path you take, and won't influence your particular path. Not high-priority. Examples: Unique bar patrons, traveling merchants (that actually travel), some minor regional military commanders, uncommon fixers, travelling fixers, minor celebrities (that you can kill off or allow to die, etc. without screwing up the future history). Good subjects for news-stories.
...
...
*Generic NPCs: Interchangeable fixers, bar patrons, random inhabitants, bartenders, etc. Examples: Bounty fixer, Patrol fixer, Merchant Fixer
...
...
*Ephemeral campaign NPCs: Specific individuals pertaining to a quest that exist (practically speaking) only for the duration of the quest. Before the quest, they don't appear. After the quest they don't appear. Example: Red-shirt wingman provided by mission-giver as assistant. Might have interesting dialog and distinct personality. Probably has a name. Might even not get blown up, but you're never going to see that NPC outside of the context of the particular quest or quest-line.

*Persistent campaign NPCs: NPCs whose persistent residence in the universe must be taken into account. You might only be able to interact with them in limited ways outside of particular quest lines, but their presence in the game universe persists in some palpable ways outside of the quest line itself.

''From ' jacks ' in ' Dramatis Personae .''</blockquote>

Development:Economy

2014-02-19T19:37:59Z

Ezee: /* CHANGES : */

== Current situation and wish list ==

Currently the economic system is quite limited (as far as playing the game has showed me). Only the player himself (or herself of course) is actually trading [[Cargo|goods]]. To create a more dynamic universe, the economy has to be extended in such a way that [[NPC]] (i.e. non-player characters, the computer-players) are also able to influence it. This will require quite some extensions. Ideas about a new economic system will be posted here and can of course be discussed.

== Future economy ==

The future economy should be more dynamic in the sense that not only the human player does trading, but the various computer players also participate. To create this, there are a number of changes required. Note that the changes described here are without any knowledge about the actual code, so there may be errors in this describtion.

The first thing needed is an improved model for the demands and offers of goods on different bases and planets. A mining base e.g. would need a huge amount of food and mining equipment, while a medical base might supply medical equipment. An indication of this system are the different prices for goods on different types of bases/planets. Usage of these goods however is not build into the game. The first task, thus, would be to create a model which describes the usage and production of goods, resulting in not only increasing amounts of goods due to production but also descreasing amounts due to consumption. Depending on the consumption and current stock, the price of the goods should be determined. This change in price can off course be used as a way to fuel trade. There are however a number of problems which need to be addressed:

1) Does a base or planet have a certain amount of [[Terminology:Credits|money]] at the start of the game and does the change with every purchase or sale or do they have an unlimmited amount of money. The major problem with the first option is that this can result in bases going bankrupt.

2) Is there a limit to the amount of products e.g. a miningbase can produce as this will result in bases being abandoned when resources are depleted.

The probable course to follow for these problems is to start with bases without any limits. Introducing limits will spawn the need to add the option to start new bases on e.g. asteroids with valuable resources, which is a large project itself.

The main goal on this change is to provide a basic infrastructure to allow trading by [[NPC]]s. To achieve this the modal of a NPC has to be extended. They should be aware of prices on the different bases and should be able to figure out a nice trading route. This in itself isn't really hard as it's just calculating the profit per distance (or time) traveled of all known [[Cargo|goods]] and selecting the highest. Besides this parameters like the type of the goods (and thus the space usage), the amount available on bases, etc need to be taken into account.

== Current Proposal ==
Reworking the Vega Strike Economy:
A Three-Fold Approach

After extended discussions, a potential dynamic economy has been developed. The proposed approach requires three areas of development. See forum threads - [http://forums.vega-strike.org/viewtopic.php?f=6&t=10828 old (2008-2011)], [http://forums.vega-strike.org/viewtopic.php?f=11&t=19507 new (2014)].

The quest to make the Vega Strike economy dynamic and hopefully more realistic has been a long one. However, it seems to be nearing an end. Mid March of 2008 “Javier” Launched a thread to try to consolidate existing economic threads that where popping up about that time. Discussions stalled with out a definitive agreement on neither features nor scope. At the end of January 2011 “Travists” tried to revive the thread. A fairly rapid-fire series of posts followed, and a general consensus was reached early in February that same year. What was determined was that there are three areas that the economy needs include: the economy responds to its self, the universe responds to the economy, and the economy responds to major changes in the universe.

There are several points in this system that underlie the three parts of development. Any attempt at a realistic economy must include [[Supply and Demand Dynamics]]. Also implied, is that the distance goods must be transported as well as the risk in that transportation influences the price. The price, availability, and faction deployment of ships and equipment depends on manufacturing sites and overall market conditions. The manufacture of goods causes prices to reflect the cost of the goods needed to make them. Manufactured quantities of goods changes with demand. Bases are simulated separately. Traffic patterns and trade levels change to indicate the current market. Factions and corporations can alter the economy by supporting various projects. A final tweak suggested is that there is a range of population densities, radiating out from core systems, rather than the current random distribution. These have several interplays leading to the three-fold approach.

== CHANGES : ==

Changes to the main VS program are needed for the universe to respond to economic changes. These include polling of the current economic factors in ship locations and numbers. When major economic changes evolve out of the simulation the news reports on it.
The strength of factions is largely influenced by their economic standing. Likely also included here are the population distributions.
There also needs to be developed for the program a routine to calculate present supply/demand levels.
One of the major changes to the game is in the dynamic generation of the universe.
That relates to the population distribution. At present, it is all random.
To facilitate the dynamic economy being usable each faction needs a homeworld.
Populations than diminish as you go outward from them. Another change to the universe
populating process needs to look at the number of habitable planets in a system,
asteroids and nebulae to determine population and what base types there are.

The economy needs to be set up for internal responses. Ships produced at shipyards and parts at factories likely falls in here. The economic database needs an entry for each base containing each good and its interrelationship with other goods. Changes in costs radiate outwards from the affected base. After much discussion the best way to do this is generally agreed to be a flow rate number crunching system rather than simulating every ship needed to account for the transfer of goods. Also included in here are the data and coding changes for population distributions starting costs, and availability/cost of ships and upgrades being based on the location of production facilities. Should the population be set up to be fluid, then economic levels would drive any significant changes. Such population changes also would change the demand for goods. Clearly, much of the dynamics of the dynamic economy happens here.

There are also many ways that the economy needs to respond to the program.
The destruction or heavy damage of a base would change the availability of the goods that
this base produces and may increase the local need for medical and construction supplies.
Should a faction take over a base than production shifts to reflect that factions goods.
Disasters also may be triggered changing needs.
Basically anytime something happens in game that would logically change the cost and/or
availability of goods, ships, or parts needs to be responded to.

[[Category:Development]]

Development:Economy

2014-02-19T19:35:03Z

Ezee: /* CHANGES : */

== Current situation and wish list ==

Currently the economic system is quite limited (as far as playing the game has showed me). Only the player himself (or herself of course) is actually trading [[Cargo|goods]]. To create a more dynamic universe, the economy has to be extended in such a way that [[NPC]] (i.e. non-player characters, the computer-players) are also able to influence it. This will require quite some extensions. Ideas about a new economic system will be posted here and can of course be discussed.

== Future economy ==

The future economy should be more dynamic in the sense that not only the human player does trading, but the various computer players also participate. To create this, there are a number of changes required. Note that the changes described here are without any knowledge about the actual code, so there may be errors in this describtion.

The first thing needed is an improved model for the demands and offers of goods on different bases and planets. A mining base e.g. would need a huge amount of food and mining equipment, while a medical base might supply medical equipment. An indication of this system are the different prices for goods on different types of bases/planets. Usage of these goods however is not build into the game. The first task, thus, would be to create a model which describes the usage and production of goods, resulting in not only increasing amounts of goods due to production but also descreasing amounts due to consumption. Depending on the consumption and current stock, the price of the goods should be determined. This change in price can off course be used as a way to fuel trade. There are however a number of problems which need to be addressed:

1) Does a base or planet have a certain amount of [[Terminology:Credits|money]] at the start of the game and does the change with every purchase or sale or do they have an unlimmited amount of money. The major problem with the first option is that this can result in bases going bankrupt.

2) Is there a limit to the amount of products e.g. a miningbase can produce as this will result in bases being abandoned when resources are depleted.

The probable course to follow for these problems is to start with bases without any limits. Introducing limits will spawn the need to add the option to start new bases on e.g. asteroids with valuable resources, which is a large project itself.

The main goal on this change is to provide a basic infrastructure to allow trading by [[NPC]]s. To achieve this the modal of a NPC has to be extended. They should be aware of prices on the different bases and should be able to figure out a nice trading route. This in itself isn't really hard as it's just calculating the profit per distance (or time) traveled of all known [[Cargo|goods]] and selecting the highest. Besides this parameters like the type of the goods (and thus the space usage), the amount available on bases, etc need to be taken into account.

== Current Proposal ==
Reworking the Vega Strike Economy:
A Three-Fold Approach

After extended discussions, a potential dynamic economy has been developed. The proposed approach requires three areas of development. See forum threads - [http://forums.vega-strike.org/viewtopic.php?f=6&t=10828 old (2008-2011)], [http://forums.vega-strike.org/viewtopic.php?f=11&t=19507 new (2014)].

The quest to make the Vega Strike economy dynamic and hopefully more realistic has been a long one. However, it seems to be nearing an end. Mid March of 2008 “Javier” Launched a thread to try to consolidate existing economic threads that where popping up about that time. Discussions stalled with out a definitive agreement on neither features nor scope. At the end of January 2011 “Travists” tried to revive the thread. A fairly rapid-fire series of posts followed, and a general consensus was reached early in February that same year. What was determined was that there are three areas that the economy needs include: the economy responds to its self, the universe responds to the economy, and the economy responds to major changes in the universe.

There are several points in this system that underlie the three parts of development. Any attempt at a realistic economy must include [[Supply and Demand Dynamics]]. Also implied, is that the distance goods must be transported as well as the risk in that transportation influences the price. The price, availability, and faction deployment of ships and equipment depends on manufacturing sites and overall market conditions. The manufacture of goods causes prices to reflect the cost of the goods needed to make them. Manufactured quantities of goods changes with demand. Bases are simulated separately. Traffic patterns and trade levels change to indicate the current market. Factions and corporations can alter the economy by supporting various projects. A final tweak suggested is that there is a range of population densities, radiating out from core systems, rather than the current random distribution. These have several interplays leading to the three-fold approach.

== CHANGES : ==

Changes to the main VS program are needed for the universe to respond to economic changes. These include polling of the current economic factors in ship locations and numbers. When major economic changes evolve out of the simulation the news reports on it.
The strength of factions is largely influenced by their economic standing. Likely also included here are the population distributions.
There also needs to be developed for the program a routine to calculate present supply/demand levels.
One of the major changes to the game is in the dynamic generation of the universe.
That relates to the population distribution. At present, it is all random.
To facilitate the dynamic economy being usable each faction needs a homeworld.
Populations than diminish as you go outward from them. Another change to the universe
populating process needs to look at the number of habitable planets in a system,
asteroids and nebulae to determine population and what base types there are.

The economy needs to be set up for internal responses. Ships produced at shipyards and parts at factories likely falls in here. The economic database needs an entry for each base containing each good and its interrelationship with other goods. Changes in costs radiate outwards from the affected base. After much discussion the best way to do this is generally agreed to be a flow rate number crunching system rather than simulating every ship needed to account for the transfer of goods. Also included in here are the data and coding changes for population distributions starting costs, and availability/cost of ships and upgrades being based on the location of production facilities. Should the population be set up to be fluid, then economic levels would drive any significant changes. Such population changes also would change the demand for goods. Clearly, much of the dynamics of the dynamic economy happens here.

There are also many ways that the economy needs to respond to the program. The destruction or heavy damage of a base would change the availability of the goods that that base produces and may increase the local need for medical and construction supplies. Should a faction take over a base than production shifts to reflect that factions goods. Disasters also may be triggered changing needs. Basically anytime something happens in game that would logically change the cost and/or availability of goods, ships, or parts needs to be responded to.

[[Category:Development]]

Development:Economy

2014-02-19T19:31:38Z

Ezee: /* CHANGES : */

== Current situation and wish list ==

Currently the economic system is quite limited (as far as playing the game has showed me). Only the player himself (or herself of course) is actually trading [[Cargo|goods]]. To create a more dynamic universe, the economy has to be extended in such a way that [[NPC]] (i.e. non-player characters, the computer-players) are also able to influence it. This will require quite some extensions. Ideas about a new economic system will be posted here and can of course be discussed.

== Future economy ==

The future economy should be more dynamic in the sense that not only the human player does trading, but the various computer players also participate. To create this, there are a number of changes required. Note that the changes described here are without any knowledge about the actual code, so there may be errors in this describtion.

The first thing needed is an improved model for the demands and offers of goods on different bases and planets. A mining base e.g. would need a huge amount of food and mining equipment, while a medical base might supply medical equipment. An indication of this system are the different prices for goods on different types of bases/planets. Usage of these goods however is not build into the game. The first task, thus, would be to create a model which describes the usage and production of goods, resulting in not only increasing amounts of goods due to production but also descreasing amounts due to consumption. Depending on the consumption and current stock, the price of the goods should be determined. This change in price can off course be used as a way to fuel trade. There are however a number of problems which need to be addressed:

1) Does a base or planet have a certain amount of [[Terminology:Credits|money]] at the start of the game and does the change with every purchase or sale or do they have an unlimmited amount of money. The major problem with the first option is that this can result in bases going bankrupt.

2) Is there a limit to the amount of products e.g. a miningbase can produce as this will result in bases being abandoned when resources are depleted.

The probable course to follow for these problems is to start with bases without any limits. Introducing limits will spawn the need to add the option to start new bases on e.g. asteroids with valuable resources, which is a large project itself.

The main goal on this change is to provide a basic infrastructure to allow trading by [[NPC]]s. To achieve this the modal of a NPC has to be extended. They should be aware of prices on the different bases and should be able to figure out a nice trading route. This in itself isn't really hard as it's just calculating the profit per distance (or time) traveled of all known [[Cargo|goods]] and selecting the highest. Besides this parameters like the type of the goods (and thus the space usage), the amount available on bases, etc need to be taken into account.

== Current Proposal ==
Reworking the Vega Strike Economy:
A Three-Fold Approach

After extended discussions, a potential dynamic economy has been developed. The proposed approach requires three areas of development. See forum threads - [http://forums.vega-strike.org/viewtopic.php?f=6&t=10828 old (2008-2011)], [http://forums.vega-strike.org/viewtopic.php?f=11&t=19507 new (2014)].

The quest to make the Vega Strike economy dynamic and hopefully more realistic has been a long one. However, it seems to be nearing an end. Mid March of 2008 “Javier” Launched a thread to try to consolidate existing economic threads that where popping up about that time. Discussions stalled with out a definitive agreement on neither features nor scope. At the end of January 2011 “Travists” tried to revive the thread. A fairly rapid-fire series of posts followed, and a general consensus was reached early in February that same year. What was determined was that there are three areas that the economy needs include: the economy responds to its self, the universe responds to the economy, and the economy responds to major changes in the universe.

There are several points in this system that underlie the three parts of development. Any attempt at a realistic economy must include [[Supply and Demand Dynamics]]. Also implied, is that the distance goods must be transported as well as the risk in that transportation influences the price. The price, availability, and faction deployment of ships and equipment depends on manufacturing sites and overall market conditions. The manufacture of goods causes prices to reflect the cost of the goods needed to make them. Manufactured quantities of goods changes with demand. Bases are simulated separately. Traffic patterns and trade levels change to indicate the current market. Factions and corporations can alter the economy by supporting various projects. A final tweak suggested is that there is a range of population densities, radiating out from core systems, rather than the current random distribution. These have several interplays leading to the three-fold approach.

== CHANGES : ==

Changes to the main VS program are needed for the universe to respond to economic changes. These include polling of the current economic factors in ship locations and numbers. When major economic changes evolve out of the simulation the news reports on it.
The strength of factions is largely influenced by their economic standing. Likely also included here are the population distributions.
There also needs to be developed for the program a routine to calculate present supply/demand levels. One of the major changes to the game is in the dynamic generation of the universe. That relates to the population distribution. At present, it is all random. To facilitate the dynamic economy being usable each faction needs a homeworld. Populations than diminish as you go outward from them. Another change to the universe populating process needs to look at the number of habitable planets in a system, asteroids and nebulae to determine population and what base types there are.

The economy needs to be set up for internal responses. Ships produced at shipyards and parts at factories likely falls in here. The economic database needs an entry for each base containing each good and its interrelationship with other goods. Changes in costs radiate outwards from the affected base. After much discussion the best way to do this is generally agreed to be a flow rate number crunching system rather than simulating every ship needed to account for the transfer of goods. Also included in here are the data and coding changes for population distributions starting costs, and availability/cost of ships and upgrades being based on the location of production facilities. Should the population be set up to be fluid, then economic levels would drive any significant changes. Such population changes also would change the demand for goods. Clearly, much of the dynamics of the dynamic economy happens here.

There are also many ways that the economy needs to respond to the program. The destruction or heavy damage of a base would change the availability of the goods that that base produces and may increase the local need for medical and construction supplies. Should a faction take over a base than production shifts to reflect that factions goods. Disasters also may be triggered changing needs. Basically anytime something happens in game that would logically change the cost and/or availability of goods, ships, or parts needs to be responded to.

[[Category:Development]]

NPC

2014-02-19T18:44:58Z

Ezee: desc from From ' jacks ' in ' Dramatis Personae

'''NPC''' , '''N'''on '''P'''layable '''C'''haracters in Vega Strike {{Fixme}}

Let's see who are the NPC in our vegastrike universe !

And how they influence the Gameplay ( fight , economy , quests , communications )

== NPC INFLUENCE IN VEGASTRIKE 0.5.1 ==

ToDO :
*List the actual pros and cons , give links to forum threads .
*Give some scripts exerpts .
*Propose ideas for future NPC dev

== ACTUAL PROS AND CONS ==

== INFLUENCES IN THE GAMEPLAY ==

== DEV CONCEPTS ==

<blockquote>
Thinking some more on basic categories for NPCs, there are

*Universe level: noteworthy characters in the VS universe you might have some reason to interact with (heads of state, famous terrorists, individuals who played/will play key roles in previous/later events or events otherwise outside of player control, etc.)
...
...
*Time-period specific NPCs: Potentially non-specific people occupying particular positions of interest, and a hodgepodge of assorted flavor characters to give the universe a lived-in feeling and different parts of it different flavors. These people may offer specific types of quests, but not specific quests, and may not have any non-dialog interactions at all. They'll be around whatever path you take, and won't influence your particular path. Not high-priority. Examples: Unique bar patrons, traveling merchants (that actually travel), some minor regional military commanders, uncommon fixers, travelling fixers, minor celebrities (that you can kill off or allow to die, etc. without screwing up the future history). Good subjects for news-stories.
...
...
*Generic NPCs: Interchangeable fixers, bar patrons, random inhabitants, bartenders, etc. Examples: Bounty fixer, Patrol fixer, Merchant Fixer
...
...
*Ephemeral campaign NPCs: Specific individuals pertaining to a quest that exist (practically speaking) only for the duration of the quest. Before the quest, they don't appear. After the quest they don't appear. Example: Red-shirt wingman provided by mission-giver as assistant. Might have interesting dialog and distinct personality. Probably has a name. Might even not get blown up, but you're never going to see that NPC outside of the context of the particular quest or quest-line.

*Persistent campaign NPCs: NPCs whose persistent residence in the universe must be taken into account. You might only be able to interact with them in limited ways outside of particular quest lines, but their presence in the game universe persists in some palpable ways outside of the quest line itself.

''From ' jacks ' in ' Dramatis Personae .''</blockquote>

NPC

2014-02-19T13:45:42Z

Ezee:

NPC

2014-02-19T13:44:59Z

Ezee:

'''NPC''' , '''N'''on '''P'''layable '''C'''haracters in Vega Strike

Let's see who are the NPC in our vegastrike universe !

And how they influence the Gameplay ( fight , economy , quests , communications )
{{Fixme}}

== NPC INFLUENCE IN VEGASTRIKE 0.5.1 ==

ToDO :
*List the actual pros and cons , give links to forum threads .
*Give some scripts exerpts .
*Propose ideas for future NPC dev

Development:Economy

2014-02-19T12:56:10Z

Ezee: /* added CHANGES title */

== Current situation and wish list ==

Currently the economic system is quite limited (as far as playing the game has showed me). Only the player himself (or herself of course) is actually trading [[Cargo|goods]]. To create a more dynamic universe, the economy has to be extended in such a way that [[NPC]] (i.e. non-player characters, the computer-players) are also able to influence it. This will require quite some extensions. Ideas about a new economic system will be posted here and can of course be discussed.

== Future economy ==

The future economy should be more dynamic in the sense that not only the human player does trading, but the various computer players also participate. To create this, there are a number of changes required. Note that the changes described here are without any knowledge about the actual code, so there may be errors in this describtion.

The first thing needed is an improved model for the demands and offers of goods on different bases and planets. A mining base e.g. would need a huge amount of food and mining equipment, while a medical base might supply medical equipment. An indication of this system are the different prices for goods on different types of bases/planets. Usage of these goods however is not build into the game. The first task, thus, would be to create a model which describes the usage and production of goods, resulting in not only increasing amounts of goods due to production but also descreasing amounts due to consumption. Depending on the consumption and current stock, the price of the goods should be determined. This change in price can off course be used as a way to fuel trade. There are however a number of problems which need to be addressed:

1) Does a base or planet have a certain amount of [[Terminology:Credits|money]] at the start of the game and does the change with every purchase or sale or do they have an unlimmited amount of money. The major problem with the first option is that this can result in bases going bankrupt.

2) Is there a limit to the amount of products e.g. a miningbase can produce as this will result in bases being abandoned when resources are depleted.

The probable course to follow for these problems is to start with bases without any limits. Introducing limits will spawn the need to add the option to start new bases on e.g. asteroids with valuable resources, which is a large project itself.

The main goal on this change is to provide a basic infrastructure to allow trading by [[NPC]]s. To achieve this the modal of a NPC has to be extended. They should be aware of prices on the different bases and should be able to figure out a nice trading route. This in itself isn't really hard as it's just calculating the profit per distance (or time) traveled of all known [[Cargo|goods]] and selecting the highest. Besides this parameters like the type of the goods (and thus the space usage), the amount available on bases, etc need to be taken into account.

== Current Proposal ==
Reworking the Vega Strike Economy:
A Three-Fold Approach

After extended discussions, a potential dynamic economy has been developed. The proposed approach requires three areas of development. See forum threads - [http://forums.vega-strike.org/viewtopic.php?f=6&t=10828 old (2008-2011)], [http://forums.vega-strike.org/viewtopic.php?f=11&t=19507 new (2014)].

The quest to make the Vega Strike economy dynamic and hopefully more realistic has been a long one. However, it seems to be nearing an end. Mid March of 2008 “Javier” Launched a thread to try to consolidate existing economic threads that where popping up about that time. Discussions stalled with out a definitive agreement on neither features nor scope. At the end of January 2011 “Travists” tried to revive the thread. A fairly rapid-fire series of posts followed, and a general consensus was reached early in February that same year. What was determined was that there are three areas that the economy needs include: the economy responds to its self, the universe responds to the economy, and the economy responds to major changes in the universe.

There are several points in this system that underlie the three parts of development. Any attempt at a realistic economy must include [[Supply and Demand Dynamics]]. Also implied, is that the distance goods must be transported as well as the risk in that transportation influences the price. The price, availability, and faction deployment of ships and equipment depends on manufacturing sites and overall market conditions. The manufacture of goods causes prices to reflect the cost of the goods needed to make them. Manufactured quantities of goods changes with demand. Bases are simulated separately. Traffic patterns and trade levels change to indicate the current market. Factions and corporations can alter the economy by supporting various projects. A final tweak suggested is that there is a range of population densities, radiating out from core systems, rather than the current random distribution. These have several interplays leading to the three-fold approach.

== CHANGES : ==

Changes to the main VS program are needed for the universe to respond to economic changes. These include polling of the current economic factors in ship locations and numbers. When major economic changes evolve out of the simulation the news reports on it. The strength of factions is largely influenced by their economic standing. Likely also included here are the population distributions. There also needs to be developed for the program a routine to calculate present supply/demand levels. One of the major changes to the game is in the dynamic generation of the universe. That relates to the population distribution. At present, it is all random. To facilitate the dynamic economy being usable each faction needs a homeworld. Populations than diminish as you go outward from them. Another change to the universe populating process needs to look at the number of habitable planets in a system, asteroids and nebulae to determine population and what base types there are.

The economy needs to be set up for internal responses. Ships produced at shipyards and parts at factories likely falls in here. The economic database needs an entry for each base containing each good and its interrelationship with other goods. Changes in costs radiate outwards from the affected base. After much discussion the best way to do this is generally agreed to be a flow rate number crunching system rather than simulating every ship needed to account for the transfer of goods. Also included in here are the data and coding changes for population distributions starting costs, and availability/cost of ships and upgrades being based on the location of production facilities. Should the population be set up to be fluid, then economic levels would drive any significant changes. Such population changes also would change the demand for goods. Clearly, much of the dynamics of the dynamic economy happens here.

There are also many ways that the economy needs to respond to the program. The destruction or heavy damage of a base would change the availability of the goods that that base produces and may increase the local need for medical and construction supplies. Should a faction take over a base than production shifts to reflect that factions goods. Disasters also may be triggered changing needs. Basically anytime something happens in game that would logically change the cost and/or availability of goods, ships, or parts needs to be responded to.

[[Category:Development]]

Supply and Demand Dynamics

2014-02-19T10:32:03Z

Ezee: /* Reference to script files */

A part of [[Development:Economy#Current_Proposal]]

Todo :
*Explain the actual trading system in a paragraph with reference to script files ?
*Develop the idea of Supply and Demand Dynamics with example in other games ?
*What users think about the actual system ?

== Explain the actual trading system ==

A discussion in the forum could be a starting point :
[http://forums.vega-strike.org/viewtopic.php?f=19&t=15871]

<blockquote>
''VS has '''galactic-level statistical simulation''' of trading goods. The system '''simulates, numerically''', the '''effect of AI ships moving stuff around'''. I've seen the code in VS, but I haven't seen the effect as clear as it should be (hence the balancing issue I've mentioned above).

In any case, the system has the potential to behave like X3's or even better, with some love, since war zones will require supplies that will be ferried by AI in this numerical simulation, driving prices up and down.

And winning or loosing wars. Since the simulation of the economy influences supplies and supplies influence the simulation of the wars raging across the galaxy, so shortage of some supplies might mean battles lost.''
''Klauss.''</blockquote>

== Reference to script files ==
*" Trading.py "
[http://spacetechs.free.fr/VEGASTRIKEDEV/DOC/python/html/namespacetrading.html Namespace]
[http://spacetechs.free.fr/VEGASTRIKEDEV/DOC/python/html/classtrading_1_1trading.html class]
[http://spacetechs.free.fr/VEGASTRIKEDEV/DOC/python/html/trading_8py_source.html Source]

== Example in other games ? ==

The same [http://forums.vega-strike.org/viewtopic.php?f=19&t=15871 thread] takes for reference the X3 economical system :

<blockquote>
''I'm also playing X3 reunion. This one's got a very sophisticated economy system, with AI traders moving stuff around, and prices changing depending on supply of products. There's also the concept of "consumption" where factories consume resources to manufacture products. (you buy and sell the products) Then you can build your own factories, etc a bunch of more advanced trading. As an economy, I'm not sure how much of it is truly dynamic since loose systems like this could easily spin out of control. There's also a bit of strangeness in how the demand/supply works, for ex: a factory's product's price varies depending on how much stock the factory has.. That's very strange business behavior.''

kensuguro .</blockquote>

Supply and Demand Dynamics

2014-02-19T10:28:41Z

Ezee:

A part of [[Development:Economy#Current_Proposal]]

Todo :
*Explain the actual trading system in a paragraph with reference to script files ?
*Develop the idea of Supply and Demand Dynamics with example in other games ?
*What users think about the actual system ?

== Explain the actual trading system ==

A discussion in the forum could be a starting point :
[http://forums.vega-strike.org/viewtopic.php?f=19&t=15871]

<blockquote>
''VS has '''galactic-level statistical simulation''' of trading goods. The system '''simulates, numerically''', the '''effect of AI ships moving stuff around'''. I've seen the code in VS, but I haven't seen the effect as clear as it should be (hence the balancing issue I've mentioned above).

In any case, the system has the potential to behave like X3's or even better, with some love, since war zones will require supplies that will be ferried by AI in this numerical simulation, driving prices up and down.

And winning or loosing wars. Since the simulation of the economy influences supplies and supplies influence the simulation of the wars raging across the galaxy, so shortage of some supplies might mean battles lost.''
''Klauss.''</blockquote>

== Reference to script files ==
*Python class " Trading.py "
[http://spacetechs.free.fr/VEGASTRIKEDEV/DOC/python/html/classtrading_1_1trading.html reference]

*[http://spacetechs.free.fr/VEGASTRIKEDEV/DOC/python/html/trading_8py_source.html Source]
== Example in other games ? ==

The same [http://forums.vega-strike.org/viewtopic.php?f=19&t=15871 thread] takes for reference the X3 economical system :

<blockquote>
''I'm also playing X3 reunion. This one's got a very sophisticated economy system, with AI traders moving stuff around, and prices changing depending on supply of products. There's also the concept of "consumption" where factories consume resources to manufacture products. (you buy and sell the products) Then you can build your own factories, etc a bunch of more advanced trading. As an economy, I'm not sure how much of it is truly dynamic since loose systems like this could easily spin out of control. There's also a bit of strangeness in how the demand/supply works, for ex: a factory's product's price varies depending on how much stock the factory has.. That's very strange business behavior.''

kensuguro .</blockquote>

Supply and Demand Dynamics

2014-02-19T10:09:26Z

Ezee:

A part of [[Development:Economy#Current_Proposal]]

Todo :
*Explain the actual trading system in a paragraph with reference to script files ?
*Develop the idea of Supply and Demand Dynamics with example in other games ?

== Explain the actual trading system ==

A discussion in the forum could be a starting point :
[http://forums.vega-strike.org/viewtopic.php?f=19&t=15871]

<blockquote>
''VS has '''galactic-level statistical simulation''' of trading goods. The system '''simulates, numerically''', the '''effect of AI ships moving stuff around'''. I've seen the code in VS, but I haven't seen the effect as clear as it should be (hence the balancing issue I've mentioned above).

In any case, the system has the potential to behave like X3's or even better, with some love, since war zones will require supplies that will be ferried by AI in this numerical simulation, driving prices up and down.

And winning or loosing wars. Since the simulation of the economy influences supplies and supplies influence the simulation of the wars raging across the galaxy, so shortage of some supplies might mean battles lost.''
''Klauss.''</blockquote>

== Example in other games ? ==

The same [http://forums.vega-strike.org/viewtopic.php?f=19&t=15871 thread] takes for reference the X3 economical system :

<blockquote>
''I'm also playing X3 reunion. This one's got a very sophisticated economy system, with AI traders moving stuff around, and prices changing depending on supply of products. There's also the concept of "consumption" where factories consume resources to manufacture products. (you buy and sell the products) Then you can build your own factories, etc a bunch of more advanced trading. As an economy, I'm not sure how much of it is truly dynamic since loose systems like this could easily spin out of control. There's also a bit of strangeness in how the demand/supply works, for ex: a factory's product's price varies depending on how much stock the factory has.. That's very strange business behavior.''

kensuguro .</blockquote>

Supply and Demand Dynamics

2014-02-19T10:03:15Z

Ezee:

Development:Ogre:Docs:Framework

2014-02-19T09:51:03Z

Ezee: broken link !

I've decided to externalize framework documentation.
Why? To use Doxygen.

Here, the current development version's [http://www.deeplayer.com/claudio/vegastrike/documentation/UIFramework/doxygen/index.html Framework Documentation]{{fixme}} ( broken link )

HowTo:Contribute

2014-02-19T09:48:12Z

Ezee: /* Code documentation */

{{Parent link|parent=[[HowTos]]}}
----
= Introduction =
So, you want to contribute to the project? You've come to the right place.

Welcome to the '''Vega Strike Contributor's Guide'''!

There are many ways to give back to the project. Artists, coders, musicians, scripters, testers, etc. are all very welcome. This article is intended to be a jump-off point that will help you find a way to contribute to the project with your individual skill set.

Not all possible avenues of contribution are covered here, but we hope that the ones that are will help point you in the right direction.

Generally, it is best to start with something that you would like improved or included in the game. Otherwise, good places to start looking for contribution possibilities are the following pages:

For tasks that need to be done:
* [[Development:Roadmap|The roadmap]] and the current release roadmap
* [[Development:2D_Images|2D images task list]]
* [[Development:3D_Models|3D models task list]]

For modding guidelines and contribution requirements see:
* [[Development:Graphics_Requirements|Generic Graphics Requirements]]
* The [[Development|Development]] wiki portal
* The [[HowTos|HowTo Tutorials]]

= Licenses =
Please bear in mind that we are bound to accept contributions under the following licenses. This means that if you submit your work for use in Vega Strike, it will be automatically licensed under GPL unless you state one of the other licenses:
* (GPL) GNU General Public License
* (LGPL) GNU Lesser General Public License
* (GPDL) GNU General Public Documentation License
* (PD) Public Domain
* (CC-BY) Creative Commons By Attribution license
* (CC-SA) Creative Commons Share Alike license
* (CC-BY-SA) Creative Commons By Attribution Share Alike license

Please note that we do not allow licenses not mentioned above, in particular:
* (CC-NC) Creative Commons Non-Commercial license or any combination with CC-BY and CC-SA

For a more updated list, please see [[Development:Graphics_Requirements#Licenses]].

= For Artists =
There are many ways in which artists can contribute.

=== Modelling/Texturing ===
A lot of the in-game models and textures could use renovation. [[Development:3D_Models#Open_Models|Development:3D Models]] contains a list of open tasks for modellers and texture artists. Information on requirements and guidelines can be found here:
* [[Development:Model_Guidelines|Modeling]]
* [[Development:Texture_Guidelines|Texturing]]
* [[HowTos#Modeling|Tutorials]]

=== Base Images ===
There are still some bases which don't have graphics that are up-to-par with current standards. Making new base images can be easier for artists not used to modeling in-game objects, particularly because levels of detail, polygon counts, etc. are not a concern.
The only consideration to be made is that final renders should be at a square resolution.

Today, most computer screens are 4:3 screens. Therefore, the best working flow would be to render a 4:3-picture and squish it to a square. Most video cards work very well with 1024x1024 textures. Older ones have trouble with larger ones. But as technology advances higher resolutions are needed.

Preferred resolutions:
* render a 1365x1024 picture and then squish it to 1024x1024
* render a 2731x2048 picture and then squish it to 2048x2048

=== Planet Textures ===
There is a need to improve existing planetary textures with the ultimate goal to provide cinematographic quality planets.
A wiki page is specifically dedicated to explaining this task. Head over to [[Development:Orbital_Planet_Surfaces|Development:Orbital_Planet_Surfaces]] for more information.

=== Space Backgrounds ===
We could always use more space backgrounds. Backgrounds in space are sphere mapped textures arranged in a cube-shaped skybox, so you will need to give us a set of six images.

*More information can be found in [[Development:System_Backgrounds]]
*The task list for backgrounds is here: [[Development:2D_Images#Space_Backgrounds]]

=== Cargo images ===
We can always use more images of cargo. Original works and crops of existing works (under a free license or public domain) are acceptable.
Although there are thoughts on restructuring and reclassifying all cargo items, every picture for currently existing cargo will be used up to then. There are still a lot of items, many of them being alien cargo, not having a picture assigned to it yet. Especially original works of those are needed.

See the [[Development:Cargo (graphics)|cargo graphics development page]] for further details.
The assignment table for new cargo graphics is on the [[Development:2D_Images]] page and the submission and vetting process is usually done in the forums.

=== Splash screens ===
The splash screens are stored in data/animations in the "spash_screenname.ani" folder.
The configuration entry is in "vegastrike.config" around line 500 as the statement "var name=splash_screen value=splash_confed.ani"
To add a new splash screen, you'll need to create an ani folder and place the picture and image file there.
The image must be in 1:1 aspect ratio, for example 1024x1024. It will be [http://sourceforge.net/tracker/index.php?func=detail&aid=1969224&group_id=19507&atid=119507 displayed filling the user's screen], which could be 4:3, 16:10, or whatever. Current backgrounds have non-square pixels and "look right" when stretched to 4:3 (e.g. 1600x1200). i.e. their pixel aspect ratios are 4:3. Unless support is added for storing the aspect ratio somewhere e.g. in the filename as suggested in that bug report, new images should also be 4:3. It's probably a good idea to work with a high rez master copy with square pixels, and only rescale and compress to the final square texture at the end.

= For Writers =

=== Stories ===

We need stories for campaigns to be written. Without stories there are no missions and no quests.
Feel free to post your ideas in the forums.

* See also [[Development:Campaigns]]

= For Musicians =

A Vega Strike [[Music Committee]] is being established to set rules, standards and guidelines for composers and provide assistance with the task of creating music for the game. [[Music Committee|Click Here to visit the Wiki Page for More Information...]]

There are also many opportunities for voice acting, learn more at [[Development:Audio#Voice_Acting]]

= For Programmers =

=== Coding tasks ===
Vegastrike is written in C++ and uses python as procedural scripting language. The C++ Code is moving to an Object Orientated organization.

Please contact the development team for information on coding tasks that need work.
You may find more information on required tasks:
* at the [[Development#Status/task_list_pages]]
* in the [[Development:Roadmap]]
* on the [http://forums.vega-strike.org/viewforum.php?f=27 Developer Focus] forum.

Several current tasks are:
*[[Development:Ogre|The OGRE Port]]
*New simulation model

=== Scripting tasks ===
There are various scripting tasks that require attention.
We could use help with Python scripting for any of the tasks:
* improving the AI system
* Mission type scripts
* Short in-system quests
* Economic simulation
* Political simulation
* Campaign scripts
* Content authoring tools

Contact the [[Vegastrike:Project#Active_Development_Team|development team]] for more info.

=== Code documentation ===
Anybody willing to comment and document current code (or to help by removing incorrect documentation) is welcome. Please contact the development team for more information.

NEW : Version 0.5.1 Doc for C++/Python is here in Doxygen format : [[DOCs]]

= For Testers =
If you would like to help test the game, please [[HowTo:Checkout_SVN|get the SVN]] (Development Version). You may also want to contact the development team to know if any specific features need testing.

Any bugs you find can be reported at the [http://forums.vega-strike.org/viewforum.php?f=2 Bug Triage forum] or the [http://sourceforge.net/tracker/?group_id=19507&atid=119507 Sourceforge Bug Tracker].

= For Others =
There is still plenty to be done if you are not an artist, coder, etc. A lot of people "work in the trenches" to maintain and update the data set.

=== Stats work ===
Stats and playbalancing are a critical part of the game. There is currently a [[Development:Rebalance|Rebalance effort]] underway. Please contact dandandaman if you would like to assist.

=== Screenshots ===
We can always use more screenshots! [[HowTo:Take Screenshots]] provides our reasons for this, along with many helpful tips and tricks.

Please [http://forums.vega-strike.org/cpg/thumbnails.php?album=13 upload your screenshots] to the User Screenshot gallery and tell us about them in the
[http://forums.vega-strike.org/viewtopic.php?t=2404 "Call for Screenshots" forums thread].

=== Adding ships ===
Sometimes, an artist will submit a model, but will not add it to the game himself. Adding ships is pretty straightforward once you figure out how to do it, although it does take time and effort. [[HowTo:Add Ships]] explains the process in detail.
Please contact the development team or check [[Development:3D Models]] to see if there are any models pending insertion.

NPC

2014-02-19T09:18:23Z

Ezee:

NPC

2014-02-19T09:17:09Z

Ezee: NPC intro