-
Notifications
You must be signed in to change notification settings - Fork 283
transition to visp 3.0.0
This document is intended to software developers who want to migrate their code from ViSP 2.x to ViSP 3.0.0.
ViSP 3.0.0 introduced a new modular software architecture where ViSP capabilities are grouped in several modules (core, io, gui, vision…). As a result, the user will find several shared or static libraries, one for each module (libvisp_core, libvisp_io, libvisp_gui, libvisp_vision…) compared to ViSP 2.x where all algorithms were grouped in the same library (libvisp).
Next we describe most notable changes and provide details and examples of transition actions.
Source code migrates from InriaForge http://gforge.inria.fr/projects/visp/ to GitHub https://github.com/lagadic/visp.
We initiate visp_contrib a GitHub repository https://github.com/lagadic/visp_contrib intended for development of “extra” modules that are contribution from the community, or that do not have stable API, that are not well-tested or that cannot be added to ViSP due to licensing. The scheme adopted in visp_contrib could be replicated by users who want to develop additional modules based on ViSP.
You can build ViSP, so it will include the modules from visp_contrib repository. Here is the CMake command:
$ cd <parent_dir>
$ git clone https://github.com/lagadic/visp.git
$ git clone https://github.com/lagadic/visp_contrib.git
$ mkdir visp-build
$ cd visp-build
$ cmake -DVISP_CONTRIB_MODULES_PATH=../visp_contrib/modules ../visp
$ make -j4
In 2.x all headers were located in visp subfolder (visp/vpMatrix.h).
In 3.0.0 all the headers corresponding to a given module are located in visp3 folder (visp3/core/vpMatrix.h). For compatibility reasons, these headers are also available in visp folder (visp/vpMatrix.h) as for the previous release.