Table of Contents
The following is a list of links for the VE-Suite dependencies. Dependencies can be downloaded and built by the user from the following links or the pre-compiled binaries can be installed from the download page.
OpenSceneGraph (OSG) is used to manage the scenegraph (verson 1.2+)
VTK is used to render the visualization objects (version 5.0+)
CMake is needed to build the VTK
VR Juggler is used for management of the virtual environment (version 2.0.1+)
The dependencies are best installed in the following order:
CMake
VR Juggler
OpenSceneGraph
VTK
VR Juggler dependencies zip file
VR Juggler has its own set of dependencies if you are building it yourself:
GMTL 0.4.12+
Boost 1.33 1+
Cppdom 0.6.6+
openAL 0.0.8+
omniORB 4.1.0+
VRPN 0.7.03+
Java 2 SDK is needed for Juggler's java-based VRJconfig program.
wxWidgets is used to compile and run the GUI. (Click "download" on the left side menu to get to the files.) (version 2.6.2+)
Xerces is used to read and write XML. (Download xerces-c-current) (version 2.7.0+)
ACE/TAO is used for cross-platform communications. (ACE version 5.5+, TAO version 1.5+)
APR is used to generate the GUIDs. (version 1.2.8)
OPAL (Open Physics Abstraction Layer) is used as a wrapper to ODE for physics integration. (version 0.4.0)
ODE (Open Dynamics Engine) is used for physics integration. (version 0.7)
VE-Launcher was coded using Python. It can run in Python2.3 or higher. If you are running it from Python, you need to install these extensions for Python as well:
Windows: VE-Launcher requires these Win32 extensions if you are running it in Python for Windows.
VE-Launcher requires wxPython 2.6.3.3 if you are running it in Python.
To avoid dependencies problems during development, we have provided guidelines for using dependencies with VE-Suite. These are the guidelines the main VE-Suite development group follows and are provided as suggestions for other users.
Windows:
The developer must either download all the installers for a particular windows IDE and OS, or build all the dependencies for VE-Suite themselves.
The VE-Suite development team will maintain certain installers for all dependencies so that the external developers will have easier access to the current development tools.
The development libraries will be kept in the native directory structure for a respective library. This ensures that a developer is able to swap libraries as necessary for research purposes without having to change the build system.
Linux:
The developer must either download all of the dependencies' rpms, use their platform's respective package management system, or build all of the dependencies for VE-Suite themselves.
The VE-Suite development team will maintain rpm files for all dependencies so that the external developers will have easier access to the current development tools.
On Linux platforms, the dependency directory structure will be assumed to be include, bin, lib, and share as is the case for most libraries when the install target is used on a build system.