Difference between revisions of "HowTo:VCPP Compiling"

From VsWiki
Jump to: navigation, search
Line 2: Line 2:
 
| previous=[[HowTo:Checkout CVS|Checkout CVS]]
 
| previous=[[HowTo:Checkout CVS|Checkout CVS]]
 
| up=[[HowTos]]
 
| up=[[HowTos]]
−
| next=[[HowTo:VCPP Toolkit Compiling|Visual C++ Toolkit Compiling]]
+
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
 
}}
 
}}
 
----
 
----
 
{{attention}}
 
{{attention}}
−
=Compiling under VCpp=
+
=Compiling under Visual C++=
 
When another module (e.g. <code>vegastrike</code>, <code>texturizer</code>), they should be placed in the directory above <code>vega-proj</code> in the directory tree.
 
When another module (e.g. <code>vegastrike</code>, <code>texturizer</code>), they should be placed in the directory above <code>vega-proj</code> in the directory tree.
  
Line 52: Line 52:
 
</pre>
 
</pre>
  
−
==Visual C++ 7.x==
+
==Visual Studeo 7.x==
 +
 
 +
===Compiling from the command line with Visual Studeo===
 
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:
 
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>
 
<pre>
Line 75: Line 77:
 
'''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.
 
'''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 vegastrike with the Visual C++ GUI===
+
===Compiling with the Visual Studeo GUI===
 
''(This is written with Visual C++ .NET Standard in mind)''
 
''(This is written with Visual C++ .NET Standard in mind)''
  
−
Once you have checked out the vegastrike and vega-vc7 modules, use VC++ 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".
+
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studeo 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 in order to install the toolkit.
 +
 
 +
===Downloads===
 +
* Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&amp;displaylang=en Visual C++ Toolkit 2003] from the Microsoft web site.
 +
* Install the [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&amp;displaylang=en Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
 +
* Install the [http://www.codeblocks.org/modules.php?op=modload&amp;name=Downloads&amp;file=index&amp;req=viewdownload&amp;cid=1 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 "C:\Program Files\Microsoft SDK\bin" 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->''' in the menu.
 +
 
 +
 
 +
=See Also=
 +
* [[HowTo:Checkout CVS|Checking out CVS]]
 +
* [http://www.codeblocks.org Code:Blocks IDE]
  
 
----
 
----
Line 84: Line 107:
 
| previous=[[HowTo:Checkout CVS|Checkout CVS]]
 
| previous=[[HowTo:Checkout CVS|Checkout CVS]]
 
| up=[[HowTos]]
 
| up=[[HowTos]]
−
| next=[[HowTo:VCPP Toolkit Compiling|Visual C++ Toolkit Compiling]]
+
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
 
}}
 
}}
  
 
[[Category:HowTos|VCpp Compiling]]
 
[[Category:HowTos|VCpp Compiling]]

Revision as of 06:08, 26 July 2005

arrow_left.png Checkout CVS arrow_up.png HowTos Cygwin Compiling arrow_right.png

This article is in need of attention. Please improve it in any way you see fit.

Compiling under Visual C++

When another module (e.g. vegastrike, texturizer), they should be placed in the directory above vega-proj in the directory tree.

For example, when you want to checkout Vegastrike, you may make a Vegastrike directory and from there, checkout vega-proj (or vega-vc7 for ".NET" users), vegastrike, data and then maybe texturizer or vssetup ALL from this directory.

  • vegastrike/ - base directory.
  • vegastrike/vegastrike/ - The stuff from the vegastrike module (the actual code)
  • vegastrike/vega-proj/ - The project files. (VISUAL C++ 6.x)
  • vegastrike/vega-vc7/ - The project files. (VISUAL C++ 7.x)
  • vegastrike/vssetup/ - the vssetup module directory.
  • vegastrike/texturizer/ - If you want to compile the texturizer.
  • data4.x - The newer version of data. Does not need -kb

module data (the old data module) is the one exception to this rule. Can be put anywhere on your hard drive. DATA (NOT data4.x, only data) MUST BE CHECKED OUT WITH THE -kb PARAMETER (=BINARY MODE)

Here is a list of every project included for CVS compilation:

  • AsterGet (AsterGen.exe)
  • mission (Mission Launcher.exe)
  • savegame (Launcher.exe)
  • texturizer (Texturizer.exe)
    • REQUIRES texturizer module
  • TriSort (TriSort.exe)
  • vsacctserver (accountserver.exe)
  • vegastrike (Vegastrike.exe)
  • vsserver (vegaserver.exe)
  • vssetup (Setup.exe)
    • REQUIRES vssetup module

Visual C++ 6.0

Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in makeall.bat), if you were going somewhere for a few hours and wanted to get a working project when you got back: 

mkdir vegastrike
cd vegastrike
@echo ***type in <enter> for prompted password***
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co vega-proj
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co vegastrike
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co vssetup
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co texturizer
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co -kb data4.x
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike logout
cd vega-proj
msdev vegastrike.dsw /MAKE ALL

Visual Studeo 7.x

Compiling from the command line with Visual Studeo

Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in makeall.bat), if you were going somewhere for a few hours and wanted to get a working project when you got back: 

@echo off
mkdir vegastrike
cd vegastrike
echo ***** Type in {ENTER} for password when asked *****
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co vega-vc7
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co vegastrike
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co vssetup
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co texturizer
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike co data4.x
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/vegastrike logout
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..

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

Compiling with the Visual Studeo GUI

(This is written with Visual C++ .NET Standard in mind)

Once you have checked out the vegastrike and vega-vc7 modules from CVS, use Visual Studeo 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 free download from Microsoft, and is the same compiler and linker as Visual Studio 2003. Note, you must have Windows XP in order to install the toolkit.

Downloads

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 "C:\Program Files\Microsoft SDK\bin" 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 CVS, import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using Project->Import-> in the menu.


See Also

arrow_left.png Checkout CVS arrow_up.png HowTos Cygwin Compiling arrow_right.png
Retrieved from "https://wiki.vega-strike.org/mediawiki/index.php?title=HowTo:VCPP_Compiling&oldid=3495"