The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Did you check errata to the book?
It says:
... Assuming (as in Chapter 2) your workspace is ~/catkin_ws, the following commands would create a basics package in that workspace that depends on rospy:
user@hostname$ cd ~/catkin_ws/src
user@hostname$ catkin_create_pkg basics rospy
The examples and discussion in Chapter 3 should then work as expected, in the ~/catkin_ws/src/basics directory. The other way to make the examples work in this chapter, besides typing them in manually, is to clone this entire repository; then you will have the basics directory (with all the examples) that you can symlink into your workspace. For example, assuming there is an existing workspace in ~/catkin_ws
user@hostname$ git clone https://github.com/osrf/rosbook ~/rosbook
user@hostname$ ln -s ~/rosbook/code/basics ~/catkin_ws/src
user@hostname$ cd ~/catkin_ws
user@hostname$ catkin_make
(that last step will ensure there is a valid setup file for this workspace created in ~/catkin_ws/devel/setup.bash) Then you can source the setup file of that workspace: user@hostname$ . ~/catkin_ws/devel/setup.bash and the examples should work.
Personally I would advise following the first snippet with creating a catkin package as it is way cleaner than the other approach.
| | 2 | No.2 Revision |
Did you check errata to the book?book?
It says:
... Assuming (as in Chapter 2) your workspace is ~/catkin_ws, the following commands would create a basics package in that workspace that depends on rospy:
user@hostname$ cd ~/catkin_ws/src
user@hostname$ catkin_create_pkg basics rospy
The examples and discussion in Chapter 3 should then work as expected, in the ~/catkin_ws/src/basics directory. The other way to make the examples work in this chapter, besides typing them in manually, is to clone this entire repository; then you will have the basics directory (with all the examples) that you can symlink into your workspace. For example, assuming there is an existing workspace in ~/catkin_ws
user@hostname$ git clone https://github.com/osrf/rosbook ~/rosbook
user@hostname$ ln -s ~/rosbook/code/basics ~/catkin_ws/src
user@hostname$ cd ~/catkin_ws
user@hostname$ catkin_make
(that last step will ensure there is a valid setup file for this workspace created in ~/catkin_ws/devel/setup.bash) Then you can source the setup file of that workspace: user@hostname$ . ~/catkin_ws/devel/setup.bash and the examples should work.
Personally I would advise following the first snippet with creating a catkin package as it is way cleaner than the other approach.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.