Installing and building osgART

From ARToolworks support library

Main Page > osgART > Installing and building osgART

The information on this page relates to the current version of osgART, version 1.1. For information relating to earlier versions, please see the page Installing and building osgART (older versions).

Contents 1 Building osgART from source 1.1 Prerequisites 1.1.1 Compiler 1.1.2 OpenSceneGraph 1.1.3 Video acquisition and AR tracking libraries 1.2 Specifying the location of ARToolKit 1.2.1 Windows 1.2.2 Linux 1.2.3 Mac OS X 1.3 Compiling 1.3.1 Windows (Visual Studio) 1.3.2 Mac OS X (Xcode) 1.3.3 Linux (gcc) 2 Post-installation tasks 2.1 Windows 3 Running the example(s) 3.1 Windows 3.2 Linux 3.3 Mac OS X

Building osgART from source

If you have been supplied with pre-built osgART binaries, you will not need to build osgART, and can skip to the next section. However, it is useful to build osgART to change various options and to add your own customisations.

Prerequisites

Compiler

• Windows: Microsoft Visual Studio .NET 2005 is the preferred build environment, with Microsoft Visual Studio 2003 also supported. Take note that the standard OpenSceneGraph 2.2 binary installation for Windows is set up for linking to MSVS 2005, and you may need to recompile OSG if are using MSVS .NET 2003 instead.
• Mac OS X: Xcode tools v2.4 or later are required. (Xcode Tools are available free with registration with ADC at [1].)
• Linux: GCC 4 or later is required.

OpenSceneGraph

osgART v1.1 builds against OpenSceneGraph v2.2. Later versions may also be supported.

Video acquisition and AR tracking libraries

• osgART Standard Edition: ARToolKit v2.72.1 or later is required.
• osgART Professional Edition: ARToolKit v4.3.3 or later is required, ARToolKit NFT 3.24.2 or later is optional.

Specifying the location of ARToolKit

When using ARToolKit, ARToolKit4, or ARToolKitNFT for video capture and/or tracking, you will need to set up environment variables so that the osgART project files knows where to find the directories containing these files. We define an environment variable named ARTOOLKIT_2_ROOT pointing to where the ARToolKit folder is, and if using ARToolKit Professional, another environment variable ARTOOLKIT_4_ROOT pointing to the ARToolKit4 folder, and if using ARToolKit NFT, yet another environment variable ARTOOLKIT_NFT_ROOT.

Windows

These environment variables are set up by the ARToolKit installer packages. You can check their correctness or set them manually by opening the System control panel, clicking the "Environment variables" button on the "Advanced" pane, and defining or editing the settings for the current user, or system wide.

Open the system control panel

Click the environment variables button

Enter the environment variables above (changing the paths to point to where you installed ARToolKit.

Linux

The easiest way to set these environment variables is to run the artoolkit-setenv, artoolkit4-setenv, and artoolkitnft-setenv scripts which can be found inside the share/ directory of the ARToolKit distributions.

Mac OS X

The ARToolKit environment variables can be set either by running the artoolkit-setenv, artoolkit4-setenv, and artoolkitnft-setenv scripts which can be found inside the share/ directory of the ARToolKit distributions, or by manually defining the build settings ARTOOLKIT_2_ROOT, ARTOOLKIT_4_ROOT, and ARTOOLKIT_NFT_ROOT in the Xcode targets inside the osgART Xcode project file.

Compiling

Windows (Visual Studio)

Build files for Visual Studio are located inside folders named VS2003 and VS2005 inside the folder VisualStudio at the top level of the osgART distribution.

The main solution file to open is named osgART.sln. Choose "Build solution" to build the video and tracker plugins, osgART itself and the test example.

The example applications are built through a separate file named examples.sln.

Mac OS X (Xcode)

1. Unpack the archive to a convenient location, and open the file osgART.xcodeproj located inside the folder Xcode at the top level of the osgART distribution.
2. Click "Build" from within Xcode. The targets required to build osgART will be built in the correct order.

Linux (gcc)

unpack osgART into a local folder (e.g. /home/thatsme/Projects/osgART)

	$> tar xfzj osgART-x.x.tar.bz2

you unpacked osgART into /home/thatsme/Projects/osgART

	$> cd /home/thatsme/Projects/osgART/bin

You need to know where artoolkit is installed and start make

	$> gmake

For using the same build system as osgART you need bakefile. You can copy the original bakefile to a new one and add another target for your application. $> cd /home/thatsme/Projects/osgART/bin $> cp osgART.bkl MyosgART.bkl You need to edit the bakefile for making changes to the source and include directories of your project. Additionally you need to regenerate the makefile from the bakefile.

	$> bakefile -f gnu MyosgART.bkl

Post-installation tasks

Windows

Copy any required DLLs from ARToolKit(s) into the osgART/bin directory. For ARToolKit v2.x, this will include libARvideo.dll, DSVL.dll. For ARToolKit v4.x, this will include ARvideo.dll, pthreadVC2.dll.

Running the example(s)

Windows

Linux

Ensure the ARTOOLKIT_CONFIG and/or ARTOOLKIT_4_CONFIG environment variables are set correctly for the videocapture you are using. For example using GStreamer with the TV testsignal simulator you can use:

	$> echo $ARTOOLKIT_CONFIG
	videotestsrc ! identity name=artoolkit ! fakesink
 

or for using Video4Linux it should read something like this:

	$> echo $ARTOOLKIT_CONFIG
	-dev=/dev/video0 -width=320 -height=240 -palette=YUV420P
  

Please consult the ARToolKit documentation for more information how to set up video capture correctly. To run the examples the runtime linker needs to be able to load the plugins from the osgART directory. For example in a bash shell:

	$> export LD_LIBRARY_PATH=".:$LD_LIBRARY_PATH"
 

run the test example

	$> ./osgARTTest

Mac OS X