Download

Contents

• Dependencies
• Download
  • Windows
  • Linux
• CVS access
  • Windows
• Build
  • Windows
    

Dependencies

Colosseum3D depends on the following libraries/projects:

• CommonC++ > 2.0.1.13
• OpenSceneGraph >= 1.2 (or CVS version)
  • OpenProducer (CVS version)
  • OpenThreads (CVS version)
• ReplicantBody (SVN version)
• Vortex 3.0
• osgAL (SVN version)
  • OpenAL++ (now included in osgAL)
• OpenAL (CVS version)

Download

Windows plattform

The windows version should include all the compiled and linked dependency libraries. Up until version 0.80 they are all built using Microsoft VisualStudio .NET2003 (VC7.1).

Starting at 0.81 we are using VisualStudio 8.

1. Download the latest installation file (colosseum3d-xxx.exe).
2. From version 0.83 the OpenAL installation is done automatically. (Download and install OpenAL runtime environment: OpenALwEAX)
3. Run the installation file and select an installation path.
4. On some systems a log out/log in is required.
5. If you check launch Colosseum3D, a demo app will start.
6. More demos are available under START->Colosseum3D
7. To execute any .osv file from explorer, just double click it.
8. To uninstall: START->Colosseum3D->Uninstall Colosseum3D

The installation procedure does not alter the path environment variable in any way.

Linux plattform

NO LINUX VERSION AVAILABLE RIGHT NOW!

There is no precompiled package for the linux package yet. So the binary package is just a source tar-ball.
You have to unpack it and build it yourself. This requires that all the depending libraries are installed (See dependencies above).

1. Download the binary package and the Data package (make sure you take the same versions).
2. Unpack the zipped files to where you want Colosseum3D to reside (for example $Home/)
3. Set the Environment variable C3D_PATH to point at the installation directory.
   e.g. tcsh> setenv C3D_PATH $Home/Colosseum3D
4. Now to setup the necessary environment variables, source the script $C3D_PATH/setup_env.csh.
5. To build the toolkit, go to $C3D_PATH and execute autogen.sh
   tcsh> cd $C3D_PATH; ./autogen.sh
6. Make the toolkit
   tcsh> make -j4
7. Build the sample applications:
   tcsh> cd demos/osgVortex
   tcsh> ./autogen.sh
   tcsh> make -j4 install
   

CVS Checkout

If you have access to HPC2N AFS, you can checkout Colosseum3D from CVS.

Checkout under Windows

1. Install a CVS client (cygwin/Tortoise/WinCVS)
2. Mount afs directory /afs/hpc2n.umu.se/projects as drive P for example.
3. Set CVS root to p:\Colosseum3D\Repository
4. checkout Colosseum3D (cvs co -r Colosseum3D_1.0)
5. Setup an environment variable C3D_DEPENDENCIES_PATH to point to where all the dependencie libraries are located.
6. checkout c3ddeps_dev (cvs co c3ddeps_dev) into C3D_DEPENDENCIES_PATH
7. Also make sure you have the following libraries checked out and built in C3D_DEPENDENCIES_PATH
   1. OpenSceneGraph
   2. OpenAL++
   3. osgAL
   4. ReplicantBody
   5. cmltoolkit_2.5
8. Setup your runtime environment
9. Go to the %C3D_PATH% directory and execute buildall.bat

Build

Windows

1. Start a Command prompt window
2. Set an environment variable C3D_PATH to wherever you checked out Colosseum3D
   (set C3D_PATH=c:\tools\colosseum3d)
   
3. Set an environment variable C3D_DEPENDENCIES_PATH to wherever you checked out c3ddeps_dev
   (set C3D_DEPENDENCIES_PATH=c:\tools\)
4. You should have osgAL, openal++, cmltoolkit_2.5, OpenSceneGraph in the path pointed out by C3D_DEPENDENCIES_PATH, if not you have to update the setup_env.bat in the c3ddeps_dev directory.
5. If you are only interested in a few subprojects of Colosseum3D, for example VRUTILS+ConfigScript then do the following
   1. Go to Colosseum3D directory
   2. Execute build.bat visualstudio\vrutils\vrutils all /build
   3. Execute build.bat visualstudio\configscript\configscript all /build
6. If you want to build everything and you have all the dependencies (already built)
   1. Go to the Colosseum3D directory
   2. Execute buildall

Observe that the Microsoft .NET 2003 (VC7) linker sometime fails during linking of the vrutils library in Debug mode.
This will halt the build process and you have to restart the build.