An Open Architecture for Reconfigurable Tracking based on XML | Contact

Installation Guide

This is a step-by-step guide to configuring and compiling OpenTracker. After the General section, the guide splits into two parts - for a Windows and for a Unix environment.


  1. You will need the following libraries to compile OpenTracker. Download the libraries form the sites linked to and install them on your system. You might need to compile them, depending on the version you chose to download. Please refer to documentation of the respective library on how to do that. Follow also the following guide lines to build these libraries correctly.
  1. Then download OpenTracker and unpack the distribution file into a directory.


  1. We recommend that you set up the following environment variables for your OpenTracker environment (under Windows 2000/NT, use the System control panel, Advanced/Environment variables section to do this):

    • Set OTROOT to the root directory of your OpenTracker installation (c:\dev\opentracker in our case).
    • Set ACEROOT to the root directory of your ACE_wrappers installation (c:\dev\ace in our case).
    • Set XERCESCROOT to the root directory of your Xerces installation (c:\dev\xerces in our case).
    • Make yourself sure that your PATH environment variable contains %ACEROOT%\bin and %XERCESCROOT%\bin.
    • Set any additional evironment variables for additional device drivers:
      • ARTOOLKITROOT for the ARToolkit library
      • VRPNROOT for VRPN inclusion-

    Of course you can work without this setup and edit your project files to fit your particular needs. However, we do not recommend this as we will continue to distribute pre-configured Visual C++ workspace files that you would need to manually edit for every new version of OpenTracker.

  2. Open the file config_win.h and uncomment the defines for any additional code you want to compile. This may include device drivers or other nodes. Typically these classes depend on special libraries that need to be present. Look at the documentation of those classes to see how to setup the build process. Also make sure the include files and libraries can be found by the compiler. Either add them to the project files or better still to the following environment variables :

    • Set INCLUDE to any include directories you will need to compile in for support of additional libraries.
    • Set LIB to any lib directories you will need to link with.


  3. Compiling the current version of OpenTracker should be a very straightforward task. If you have installed the necessary external libraries in proper places as specified above, the only step you need would be to open opentracker.dsw located in the topmost directory of the OpenTracker source tree and perform a Batch build that builds the OpenTracker library plus the standalone program.

The build process builds a DLL for OpenTracker, either called opentracker.dll or opentrackerd.dll for the debug version and a standalone program called opentracker.exe to use as standalone tracking server. All output files will be in %OTROOT%\bin and the library files in %OTROOT%\lib.


  1. Go to the root directory of your OpenTracker installation.

  2. run "scons" to compile OpenTracker

  3. run "scons install" to install it your system.

  4. Make sure that any shared libraries OpenTracker needs ( such as ACE and Xerces ) are accessible ( in a lib directory or in LD_LIBRARY_PATH ) so that the binaries will be able to execute. We als provide debian packages for the most recent version of ACE and other necessary or optional libraries to run and compile OpenTracker on Debian Linux, e.g. OpenVideo, TinyXML, Muddleware, Coin3D, SoQt. Just add the line

    deb unstable main

    to your /etc/apt/sources list. Alternatively you can manually download the packages from the above URL and run:

    $ dpkg -i <package name>

copyright (c) Graz University of Technology | Webmaster