ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Yes, but you'll have to build it from sources. See moveit.ros.org/install/source for details.

Yes, but you'll have to build it from sources. See moveit.ros.org/install/source for details.


Edit:

I'm very new to ROS and MoveIt!.

A bit harsh maybe, but I believe you'd use the same techniques / follow a similar procedure with any open-source software.

I understand that i have to pull down required repositories and build it within my catkin workspace.

If you follow the steps described on the MoveIt Install page that will mostly be done for you, but that is the general idea, yes.

But how do i know which version i will be building?

That is more a general software version control question: typically something like a tag (or sometimes a special branch) is used to associate a version number with a specific state of the software repository. On GitHub, those tags are then most of the times accompanied by releases, that can be found on a special page for a specific repository. For MoveIt, you can find the releases at ros-planning/moveit/releases.

With semantic versioning, releases are always numbered as major.minor.patch. MoveIt uses different minor numbers for the different ROS distributions that it supports: 9 for Kinetic, 8 for Jade and 7 for Indigo. So you'll want to find a release (tag) that is of the form 0.7.x if you're targeting Indigo.

Once you've determined the particular release you'd like to build -- and after you've completed the wstool merge .. and wstool update steps from the instructions (but before rosdep ..), cd into the moveit, moveit_msgs and moveit_resources and do a git checkout RELEASE_TAG in each of those directories, where RELEASE_TAG is the specific version that you'd like to build. After that you can continue with the rest of the instructions.

Note that not all involved packages have the same versions / tags. You'll have to select a matching set yourself. You could use the CHANGELOG or perhaps even the repo sync announcements in the Discourse release category.