ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
![]() | 1 | initial version |
This is because we didn't do the necessary steps yet which are necessary to let our stacks get build and published as .debs via Willow Garage's build system. I'll have to check how that works, but with a major robotic competition coming up next week it'll probably be 2 weeks till I get to do it. You can always manually check out and build everything e.g. using
svn checkout http://tu-darmstadt-ros-pkg.googlecode.com/svn/trunk/ tu-darmstadt-ros-pkg-read-only
Note that the path of this checked out working copy has to be inside the ROS_PACKAGE_PATH as described here.
You should the be able to build packages using for example
rosmake hector_mapping
![]() | 2 | No.2 Revision |
This is because we didn't do the necessary steps yet which are necessary to let our stacks get build and published as .debs via Willow Garage's build system. I'll have to check how that works, but with a major robotic competition coming up next week it'll probably be 2 weeks till I get to do it. You can always manually check out and build everything e.g. using
svn checkout http://tu-darmstadt-ros-pkg.googlecode.com/svn/trunk/ tu-darmstadt-ros-pkg-read-only
Note that the path of this checked out working copy has to be inside the ROS_PACKAGE_PATH as described here.
You After performing the above steps, you should the be able to build packages using for example
rosmake hector_mapping
![]() | 3 | No.3 Revision |
This is because we didn't do the necessary steps yet which are necessary to let our stacks get build and published as .debs via Willow Garage's build system. I'll have to check how that works, but with a major robotic robotics competition coming up next week it'll probably be 2 weeks till I get to do it. You can always manually check out and build everything e.g. using
svn checkout http://tu-darmstadt-ros-pkg.googlecode.com/svn/trunk/ tu-darmstadt-ros-pkg-read-only
Note that the path of this checked out working copy has to be inside the ROS_PACKAGE_PATH as described here.
After performing the above steps, you should the be able to build packages using for example
rosmake hector_mapping