ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I guess you cloned the groovy version from branch groovy-devel of the hector_gazebo stack from github. Please try again with the fuerte-devel branch, if you are using fuerte. The gazebo version that comes with groovy uses a newer API version and the groovy-devel branch will not compile any more with gazebo version 1.0.2 in fuerte.
We recently moved most of our tu-darmstadt-ros-pkg stacks from Google Code to GitHub (see https://github.com/tu-darmstadt-ros-pkg). The default branch is set to groovy-devel, so you have to specify the fuerte-devel branch explictly, e.g.
git clone https://github.com/tu-darmstadt-ros-pkg/hector_gazebo.git -b fuerte-devel
or using rosws:
rosws set hector_gazebo --git https://github.com/tu-darmstadt-ros-pkg/hector_gazebo.git --version fuerte-devel
Unfortunately the name of the development branch to use for each distro is currently not displayed in the ROS wiki. I opened a feature request issue here.
2 | fixed rosws command line |
I guess you cloned the groovy version from branch groovy-devel of the hector_gazebo stack from github. Please try again with the fuerte-devel branch, if you are using fuerte. The gazebo version that comes with groovy uses a newer API version and the groovy-devel branch will not compile any more with gazebo version 1.0.2 in fuerte.
We recently moved most of our tu-darmstadt-ros-pkg stacks from Google Code to GitHub (see https://github.com/tu-darmstadt-ros-pkg). The default branch is set to groovy-devel, so you have to specify the fuerte-devel branch explictly, e.g.
git clone https://github.com/tu-darmstadt-ros-pkg/hector_gazebo.git -b fuerte-devel
or using rosws:
rosws set hector_gazebo --git https://github.com/tu-darmstadt-ros-pkg/hector_gazebo.git --version fuerte-devel
--version=fuerte-devel
Unfortunately the name of the development branch to use for each distro is currently not displayed in the ROS wiki. I opened a feature request issue here.