Skip to content
ViSP stack for ROS
Branch: master
Clone or download

ViSP stack for ROS


vision_visp provides ViSP algorithms as ROS components. ViSP visp is the Visual Servoing Platform and ROS ros a robotics middleware.

These packages are released under the GPL-2 license.

Components documentation is hosted on the [ wiki] vision_visp-wiki.

Support is provided through [ROS Answers] vision_visp-answers .

Which branch should I use?

Branches come in two flavors:

  • development branch,
  • release branch

Package for each ROS release is maintained on separate branches. I.e. melodic-devel is the Melodic Morenia development branch whereas melodic is the Melodic Morenia release branch.

master means the next ROS release.

If you are a user you should use a release branch as they contain stable and tested versions of the packages. If you are a developper you must provide new patches against master. You may also provide version-specific bug fix again older releases.

  • Never implement new features in old branches (i.e. not master). These Pull Requests will not be accepted. If you provide a bug fix then you may ask for it to be backported. ABI/API breakage prevent patches from being backported.
  • The only action allowed in release branches is merging the development branch in the current branch.

Warning: the Fuerte branches still rely on the legacy rosbuild build system. We recommend you to update to a newer ROS release. Only minimum maintained will be done for this release.

Additional development guidelines are provided in

Build Status

This stack supports the following ROS releases:

  • Hydro
  • Groovy
  • Fuerte
  • Indigo
  • Jade
  • Kinetic
  • Lunar
  • Melodic

The master branch holds the development that will be available in the next ROS release.

ROS Release Development Branch Release Branch
Master Build Status N/A
Melodic Build Status Build Status
Lunar Build Status Build Status
Kinetic Build Status Build Status
Indigo Build Status Build Status
You can’t perform that action at this time.