1. Setting up IVT
1.1. Downloading the IVT
Download the newest version of the IVT, e.g.
ivt-1.3.7.zip, at http://sourceforge.net/projects/ivt/ in the download area.
In a console window, change to the directory of the downloaded archive and then run the command
unzip ivt-1.3.5.zip. After unpacking, the directory
IVT should exist in the current directory.
The IVT offers the possibility of configuring the library before building it. This configuration takes place in the file
IVT/src/Makefile.base. In order to change the default settings, the file
Makefile.base must be opened and edited with a text editor (e.g. vim). In the following, the most important configuration options available under Mac OS X are listed. These options are configuration variables, which can be set either to 1 or 0. In order to integrate or exclude certain parts of the IVT library, the appropriate configuration variable must be set to 1 for integration and to 0 for exclusion.
The IVT library implements an own multi-platform GUI toolkit, which is used by the example applications. Under Mac OS X, a Cocoa implementation is available, which can be activated with this flag. When setting USE_COCOAGUI = 1, then USE_QTGUI = 0 must be set.
The IVT library allows easy access to OpenGL and GLU. The GUI toolkit of the IVT allows the creation of GL widgets. Furthermore, the class
COpenGLVisualizersets up the projection model for a given instance of the class
The IVT library implements a Quicktime video capture module with the class
The IVT library optionally integrates calls to the OpenCV library. The file names of the source files implementing encapsulated calls to the OpenCV have the ending
HighGUI is part of the OpenCV library. It is needed for the optional IVT classes
COpenCVWindowand the namespace
Apart from these variables, the directory paths to include and library files as well as the file names of the libraries can be changed in the lower part of the file. The pre-configured paths usually correspond to the default installation paths. Modifying the paths is only recommended, if problems arise with the default paths. For manual adjustment of the paths, a short explanation of the appropriate variables is given in the following:
Contains all directory paths to included files. Adding a path takes place by using the operator += and adding the path with the leading parameter -I. For example INCPATHS_BASE += -I/usr/X11R6/include
Contains all directory paths to library files. Adding a path takes place by using the operator += and adding the path with the leading parameter -L. For example LIBPATHS_BASE += -L/usr/X11R6/lib
Contains all file names of the libraries. Adding a file name takes place by using the operator += and adding the file name with the leading parameter -l. For example LIBS_BASE += -lGL -lGLU
1.4. Building the IVT libraries
The libraries are built by running the command
make in the directory
IVT/src. If after having built the IVT library once, modifications are made to the IVT files located in
IVT/src, it is recommended to run the command
make clean before running the command
make, in order to enforce a complete new build process.
1.5. Example application
For checking the installation, and as an introduction to programming with the IVT, the most simple example application is SimpleApp. SimpleApp doesn't use a GUI and thus doesn't require Qt or any other libraries to be installed. It is found in
IVT/examples/SimpleApp. After changing to the directory
SimpleApp, an executable file with the name
simpleapp is created by running the command
make. If the application is started with
then a file called
output.bmp is produced in the same directory. There are numerous further example applications in the directory
IVT/examples, with which the features of the IVT can be tested and learned. For checking Qt support, e.g. the example application in
IVT/examples/FilterDemo can be used.