[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

2.4.2 Microsoft Visual C++ 7, 7.1 or 8

Originally written by Philip Wyett philwyett@gmx.com. Last updated 18 May 2005.

In order to successfully compile the Crystal Space 3D Software Development Kit (SDK), you will need a copy of Microsoft Developer Studio .NET or the stand alone version of Microsoft Visual C++ 7 (.NET 2002), Microsoft Visual C++ 7.1 (.NET 2003) or Microsoft Visual C++ 8 (.NET 2005). The Express Edition of MSVC 8 is perfectly suitable to compile Crystal Space, once the Platform SDK was installed (more below).

Getting Extra Help

If you need help with Crystal Space and Visual C++ or just Crystal Space in general. You can subscribe and then post a message to the Crystal Space mailing list. To subscribe see the following site and fill in the form:

http://lists.sourceforge.net/lists/listinfo/crystal-main

Required/Optional External Libraries and Software

All the following libraries and Software Development Kits (SDK) unless stated are not required. However, if you choose not to install them, at compile time you must follow the documented instructions of how to unload these projects from the Crystal Space build process.

Platform SDK - required for Microsoft Visual C++ 2005 Express Edition

All supported versions of Microsoft Visual C++ ship with a version of the Platform SDK that suffices to compile Crystal Space, except the Microsoft Visual C++ 2005 Express Edition, which requires a seperate setup of the Platform SDK. Follow these instructions exactly to set up the PSDK:

http://msdn2.microsoft.com/en-us/vstudio/aa700755.aspx

cs-win32libs - Required

Before you attempt to compile Crystal Space, you must download and install the “cs-win32libs” archive. This archive contains alot of the third party header, pre-built libraries and dll files used by Crystal Space, i.e. ‘libz-cs.dll’, ‘libjpeg-cs.dll’, ‘libpng-cs.dll’, etc. See cs-win32libs.

Once you have downloaded the cs-win32libs package, execute the binary and follow the setup instructions. You may want to select “VC typical” in the “Select Components” screen. You can further adjust the selection of installed components depending on your actual set up (e.g. install MinGW-related components if you plan to also use CrystalSpace with MinGW/MSYS).

DirectX - Optional

In order to compile Crystal Space at its minimum i.e. the software renderer, you must have at least some form of the DirectX Software Development Kit (SDK) on your system.

Visual C++ 7 and later come with the minimum required DirectX SDK 8.1 files in order to build Crystal Space.

The “cs-win32libs” package also come with minimum headers and libraries that suffice to compile the parts of Crystal Space that utilize DirectX. However, the version included in cs-win32libs is DirectX 7, so you may want to stick to the DirectX 8.1 shipped with VC++ 7.

You can optionally download the latest DirectX Software Development Kit (SDK), which can be obtained from:

http://www.msdn.microsoft.com/directx

Thanks, to the miracle which is Microsoft. If you download and install the latest DirectX Software Development Kit (SDK) and already have Visual C++ installed, it will ask you if you wish to add the paths to the SDK to Visual C++ so it can use it. We recommend you accept when offered this option. If it is not the latest SDK you install you will have to manually point Visual C++ to where you installed the SDK in-order for it to be used. This can be done from the Visual C++ file menu and selecting Tools->Options->Directories. You must add the paths for both the include files and libraries and being that we wish Visual C++ to see and use this new SDK before all possible others on your system, you must click on and drag both paths you have entered to the top of the list.

Python - Optional

Crystal Space contains support for Python scripting and thus has projects within it requires that Python be installed on your system. Make sure you add the Python include and libs directories to MSVC so that the compiler can see those files. If you wish to compile with Python support you must install Python 2.2 or later, which can be obtained from:

http://www.python.org

NOTE: To have parity with one of the latest versions of msvc_libs and take full advantage of the debug elements - you should have Python 2.2.3 or 2.3.0 installed on your system. Whichever version you decide to use, make sure you download the comparable msvc_libs.

Compiling Crystal Space

To compile Crystal Space, you'll have to perform the following steps. If anything doesn't work, see the Win32 FAQ, MSVC7 FAQ.

  1. Load ‘CS\mk\msvcN\wkstypical.sln’, where ‘N’ must be replaced with the version number of the MSVC version you use.
  2. From the file menu select Build->Build Solution. Note: If you want to build a debuggable version of Crystal Space, you should select the Debug build mode; otherwise select the Release build mode. Do not use the special-purpose ExtensiveMemDebug build mode.
  3. After a while the compilation should finish. The signal for a successful build will be come in the form of the something similar to the following:
     
    Build: 1 succeeded, 0 failed, 0 skipped
    

Running the Demonstration Applications

The first app you should try is Walktest. This program shows many of the features of the 3D engine. You can run it by starting it from the windows explorer. It should be at ‘.../cs/walktest.exe’. Don't start it from other locations or from within Visual Studio. It won't find the required files if you do.

If you want to run a debug session, you first have to set the working directory. First select the project you wish to debug and setting it as the startup project. Next open Project->Properties->Debugging and enter the base ‘CS\’ directory as the working directory for debug sessions (for example, ‘C:\CS\’). Be sure to to this for Debug and Release builds.

You can now continue with the next platform-independent step. The remaining Windows-specific sections are only important when you want to compile your own application using Crystal Space.

Structure of the Workspace

Note: If you find bugs in the MSVC project or workspace files coming with Crystal Space, don't send fixes for these files to the developers. These files are generated automatically, so your fixes would be useless. Better, send a description of the bug to the mailing list.

The Crystal Space workspace is divided into several projects. They all exist as separate project files (‘*.vcproj’). The projects are collected together by workspaces ‘*.sln’. A workspace will also ensure correct linking between the various projects. There are several workspaces to choose from. Most users should choose the typical workspace, but the others are available for the adventurous.

The workspace uses a prefix system for naming contained projects:

The Libraries are C++ libraries that you can link into your own programs. Some of these libraries are part of the core of Crystal Space. Their output are ‘.lib’ files.

The Plugins are also programming libraries, but they use a special mechanism called SCF as their interface to your program. This separates their interface from the internals of the library and thus allows dynamic linking. In fact, some of the Libraries also use SCF. The rule for the MSVC workspace is simple: The Plugins are projects that build a dynamic library (‘.dll’). You can find more information in the section of this manual dealing with plug-in modules. See section Plugins, Reference counting, Interfaces (SCF).

The Applications are programs using some of these libraries, so they produce ‘.exe’ files.

Compiling Your Own Program Using Crystal Space

There is a HOWTO which explains how to create an MSVC project file for your own program which utilizes Crystal Space. See section Creating an External MSVC 7, 7.1, 8 or 9 Application.

Frequently Asked Questions (FAQ)

This is the list of frequently asked questions for the Win32 port of Crystal Space. Please consult this list if you are having difficulty building or using the project.

Building

Executing

Miscellaneous


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

This document was generated using texi2html 1.76.