ViSP  2.9.0
Tutorial: Installation from source on Linux Fedora

In this tutorial you will learn how to install ViSP from source on Linux Fedora. These steps have been tested for Fedora 18 (64 bit) distribution, but should work with any other distribution as well.

Concerning ViSP installation, we provide also other tutorials

ViSP can also be installed on other platforms including OSX, CentOS, openSUZE (see Install from source page).

Required packages

  • gcc 4.4.x or later. This can be installed with:
    su -c "yum install gcc-c++"
  • CMake 2.6 or higher that could be installed with:
    su -c "yum install cmake"

ViSP is interfaced with several optional third-party libraries. The installation of the corresponding packages is described in Optional 3rd party packages section.

Getting ViSP source code

There are different ways to get ViSP source code:

  • You can download the latest stable release as a zip or a tarball. Once downloaded, uncompress the file using either
    tar xvzf ViSP-2.9.0.tar.gz
  • You can also download a more recent snapshot. Once downloaded, uncompress the file using
  • Or you get the cutting-edge ViSP from Subversion repository. To this end you have first to install subversion
    su -c "yum install subversion"
    and then use the following command
    svn checkout svn:// ViSP-trunk

We suppose now that ViSP source is in a directory denoted <source_dir>, for example $HOME/ViSP-2.9.0

Configuring ViSP from source

  • Create first a directory denoted <binary_dir> where you want to build ViSP. This directory will contain generated Makefiles, object files, and output libraries and binaries.
    cd $HOME; mkdir ViSP-build-release
  • Enter the <binary_dir> and to configure the build type:
    cmake [<optional parameters>] <source_dir>
    For example:
    cd $HOME/ViSP-build-release
    A more versatile way to configure the build is to use ccmake, the CMake GUI:
    ccmake ../ViSP-2.9.0
    The following image shows that this command allows to configure (just by pressing [c] key) the build in a more advanced way where some options could be easily turned On/Off. It allows also to see which are the 3rd party that will be used.
    Snapshot of the ccmake ../ViSP-2.9.0 command used to configure ViSP.
  • There is an other way to see which are the 3rd party that are found during the configuration stage and that will be used by ViSP during the build. To this end you can have a look to the text file named ViSP-third-party.txt and located in <binary_dir>. We provide hereafter an example of a possible content of this file:
    ViSP third-party libraries
    Below you will find the list of third party libraries used to
    build ViSP on your computer.
    Gnu Scientific Library : no
    Lapack/blas : no
    Ogre simulator : no
    \- Ogre3D : no
    \- OIS : no
    Coin simulator :
    \- Coin3D : no
    \- SoWin : no
    \- SoXt : no
    \- SoQt : no
    \- Qt4 : no
    \- Qt3 : no
    Afma6 : no
    Afma4 : no
    Biclops : no
    Ptu46 : no
    Pioneer : no
    Viper S650 : no
    Viper S850 : no
    Cycab : no
    Video devices (display)
    X11 : no
    GTK : no
    OpenCV : no
    GDI : no
    Direct3D : no
    Firewire libdc1394-1.x : no
    Firewire libdc1394-2.x : no
    Video For Linux Two : no
    DirectShow : no
    CMU 1394 Digital Camera SDK : no
    OpenCV : no
    Specific devices
    Yarp : no
    Kinect : no
    \-libfreenect : no
    \-libusb-1.0 : no
    \-pthread : yes
    Video and image Read/Write:
    FFMPEG : no
    libjpeg : no
    libpng : no
    XML2 : no
    pthread : yes
    OpenMP : yes
    Doxygen : no
    Graphviz dot : no
    ViSP built with C++11 features: no
    In our case, only pthread an OpenMP 3rd party are detected.

Optional 3rd party packages

As mentioned previously, ViSP is interfaced with some 3rd party libraries. The complete list is provided here. We recommand to install the following:

  • OpenCV
    su -c "yum install opencv-devel"
  • libX11 to be able to open a window to display images
    su -c "yum install libX11-devel"
  • lapack and gsl to benefit from optimized mathematical capabilities
    su -c "yum install lapack-devel gsl-devel"
  • libdc1394 to grab images from firewire cameras
    su -c "yum install libdc1394-devel"
  • libv4l to grab images from usb or analogic cameras
    su -c "yum install libv4l-devel"
  • Coin, to be able to support vrml cad model used by the model-based trackers
    su -c "yum install Coin2-devel"
  • libxml2 to be able to configure the model-based trackers from xml files
    su -c "yum install libxml2-devel"
  • libjpeg, libpng to support jpeg and png images
    su -c "yum install libjpeg-devel libpng-devel"
  • ffmpeg, to be able to read or encode compressed video streams
    su -c "yum install ffmpeg-devel"
  • Ogre 3D if you want to do augmented reality or simulation
    su -c "yum install ogre-devel ogre-samples ois-devel"

Once installed, if you want that ViSP exploit the new 3rd party, you have to configure ViSP again.

ccmake ../ViSP-2.9.0

The following image shows now that all the previous optional 3rd party are detected.

Snapshot of the ccmake ../ViSP-2.9.0 command used to configure ViSP after installation of optional 3rd party libraries.

Generating Makefiles

To generate the makefiles, just press [g] key in the ccmake gui.

Now we can build ViSP.

Building ViSP from source

  • To build ViSP proceed with:
  • To install ViSP proceed with:
    sudo make install
  • To build ViSP documentation, you have first to install Doxygen package:
    su -c "yum install doxygen graphviz"
    Then you can proceed with:
    make html-doc

You are now ready to see the next Tutorial: Getting started that will show you how to use ViSP as a 3rd party to build your own project.