Build Environment

In short: How to Build

1. Download and compile OSG
2. Download osgVisual from svn: ​http://www.osgvisual.org/svn/osgvisual/osgVisual
3. Run CMAKE and select your required modules
4. Compile osgVisual

OpenSceneGraph

To use osgVisual, users have to create a build environment like OpenSceneGraph. It is recommended not to use precompiled packages but to compile osg from SVN trunk. Read ​http://www.openscenegraph.org/projects/osg/wiki/Support/GettingStarted for further details.
Windows user can use the third party requirements as precompiled packages for VS2005 and VS2008 (Watch you VS version, otherwise you'll get unpredicable compile or runtime errors!) from ​http://www.openscenegraph.org/projects/osg/wiki/Downloads/Dependencies.

In short:

• checkout osg SVN trunk
  • Linux: "svn co ​http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.7 OpenSceneGraph"
  • Windows: TortoiseSVN checkout from svn "​http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.7"
• configure osg
  • Linux:
    • Release: "./configure"
    • Debug: edit configure and change BuildType? to "Debug", then run "./configure"
  • Windows: use CMAKE: "configure"
    • Set your "Install Prefix" to the same directory as your source code
    • If you include Collada, use the static packages to avoid compile and link error (*-s.lib / *-sd.lib)
    • Use libxml2.lib for collada
    • Select your settings
    • Press "generate" to generate native build solution
• Compile and install osg:
  • Linux: "make && make install"
  • Windows: "Build ALL" as release and debug

For detailed Step-By-Step instructions look at this for Linux and Windows tutorials.

osgEarth

It is possible to use osgVisual in combination with osgEarth for terrain data. To compile osgEarth use CMAKE. Use zlib and libexpat.lib during configure.

osgVisual third party modules

osgVisual provides several moduls which rely on commercial third party modules like ​Vista2D or ​Silverlining. To use this moduls, install the packages and activate the modules during CMAKE configuration. If modules are enabled, additionally configuration options appear after running another "configure" loop. Specify the options (e.g. Silver-lining license information or paths to libraries and include files.

It is possible to run osgVisual without any commercial module.

osgVisual

• Checkout osgVisual trunk
  • Linux: "svn co ​http://www.osgvisual.org/svn/osgvisual/osgVisual osgVisual"
  • Windows: TortoiseSVN checkout from svn "​http://www.osgvisual.org/svn/osgvisual/osgVisual"
• configure osgVisual:
  • Linux: Use CMAKE GUI to select your required modules and set Build Type to "Debug" for debug puproses.
  • Windows: Use CMAKE to configure osgVisual and it's modules.
• Compile osgVisual:
  • Linux: "make"
  • Windows: "Build ALL" in debug and release version.

PlatformSpecifics

Visual Studio

Because osgVisual is mainly developed in Windows 7, CMAKE generates the VS solution user file (vcproj.user) [1] to preset:

• Command
• Working Directory
• Command Arguments

This way, you can osgVisual directly compile and use without specifying the required parameters.

Linux

Please ensure to have all dependency packages installed. Not all osgVisual modules are available for linux, for further details look at Modules?

Links

[1] ​http://stackoverflow.com/questions/1005901/how-to-set-path-environment-variable-using-cmake-and-visual-studio-to-run-test