How to build IGSTK

From IGSTK

Jump to: navigation, search

Contents

Introduction

IGSTK has two code repositories: a main IGSTK CVS and a sandbox. The main CVS repository contains the version of the code that has been reviewed, well-tested and approved for intergration. The Sandbox is a testbed for developers to experiment on new ideas before intergration with the rest of the toolkit. The main IGSTK CVS and the Sandbox are built separately.

Building IGSTK main CVS

To build IGSTK main CVS, you can download tarball/zip files from the Download page or check out the source code the from CVS. 

 cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/IGSTK login

To the password question replay with "igstk" in lower case. 

 password:   igstk

To check out latest CVS version 

 cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/IGSTK co IGSTK

To check out version 4.2 

 cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/IGSTK co -r IGSTK-4-2 IGSTK

Configuration

The configuration process starts by running CMake on the IGSTK library.

  1. You must first create a directory that will be used for receiving the binary files resulting from the build process. This directory is called the "Binary" directory hereafter.
  2. When you run CMake
    1. in Windows you run CMakeSetup.exe and provide the Source and Binary directories for IGSTK
    2. in Linux/Unix you cd into the Binary directory and from there you type ccmake "Source-Directory".

Once the source and binary directories for IGSTK have been identified, you can select the option "configure", at this point CMake will ask you for the location of the binary directory for ITK, and the binary directory for VTK.

To use IGSTK Qt widget, you have to build VTK with GUI support option (VTK_USE_GUISUPPORT) and Qt option (VTK_USE_QVTK) turned on

Once the VTK and ITK binary directories are specified, new options show up in the configuration

  1. IGSTK_USE_FLTK
  2. IGSTK_USE_Qt
  3. IGSTK_USE_MicronTracker

Depending on the options you turn on, more options will show up. For example, if you turn on the MicronTracker option, then you will need to specify the include directory for the MicronTracker package and the MicronTracker (MTC) library.

  1. MTC_INCLUDE_DIRECTORY
  2. MTC_LIBRARY

//Directory where the MTC.h file is located

  1. MTC_INCLUDE_DIRECTORY:PATH=C:/Program Files/Claron Technology/MicronTracker/Dist

//Full path to the MTC.dll file

  1. MTC_LIBRARY:FILEPATH=C:/Program Files/Claron Technology/MicronTracker/Dist/MTC.lib


If IGSTK_USE_FLTK option is turned on, then location of the binary/build directory of FLTK needs to be specified. Similar to ITK and VTK, FLTK can be build using CMake.

Additional options

  1. IGSTK_USE_OpenIGTLink ( For OpenIGTLink support, more information can be found in http://public.kitware.com/IGSTKWIKI/index.php/Using_OpenIGTLink_in_IGSTK )
  2. IGSTK_USE_VideoImager ( To build video imager support classes )

Building Sandbox

Sandbox Checkout

To check out Sandbox source code 

 cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/IGSTK login

To the password question replay with "igstk" in lower case. 

 password:   igstk


To check out latest CVS version 

 cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/IGSTK co Sandbox

To check out version 4.0 

 cvs -d :pserver:anonymous@public.kitware.com:/cvsroot/IGSTK co -r IGSTK-4-2 Sandbox

Configuration

Configuration of the sandbox is similar to the main IGSTK CVS. The only additional cmake option is a directory path to IGSTK main cvs.

Retrieved from "http://public.kitware.com/IGSTKWIKI/index.php/How_to_build_IGSTK"
Personal tools
TOOLBOX
LANGUAGES