HowTo:VCPP Compiling
Checkout CVS | HowTos | Cygwin Compiling |
Contents
Compiling under VCpp
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
- REQUIRES
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 C++ 7.x
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 vegastrike with the Visual C++ GUI
(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".
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
- Install the Visual C++ Toolkit 2003 from the Microsoft web site.
- Install the Windows Platform SDK from the Microsoft web site. You can take any of the 3 versions available.
- Install the Code::Blocks (alternative download site on Sourceforge). You can take the full version or the core only, since we will use the VS 2003 TK. Choose Visual C++ Toolkit 2003 as the default compiler. For configuration you have to include the location of the Windows Platform SDK.
Compiling with Code::Blocks and Visual C++ Toolkit
Checkout CVS | HowTos | Cygwin Compiling |