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 |
Handling of messages has changed in Fuerte. Message headers for C++ are installed in /opt/ros/fuerte/include/<package>, python files are installed in /opt/ros/fuerte/lib/python2.7/dist-packages/<package>/msg and lisp files in /opt/ros/fuerte/share/common-lisp/ros/<package>.
Generation of message files for actions are just a temporary step and the msg files themselves are normally not required for compiling ros packages. As far as I can see, they are not installed.
| | 2 | No.2 Revision |
Handling of messages has changed in Fuerte. Message headers for C++ are installed in /opt/ros/fuerte/include/<package>, python files are installed in /opt/ros/fuerte/lib/python2.7/dist-packages/<package>/msg and lisp files in /opt/ros/fuerte/share/common-lisp/ros/<package>.
Generation of message files for actions are just a temporary step and the msg files themselves are normally not required for compiling ros packages. As far as I can see, they are not installed.installed at the moment into /opt/ros/fuerte/share/actionlib/tmp/buildd/ros-fuerte-actionlib-1.8.4-0oneiric-20120406-2119/obj-x86_64-linux-gnu/actions_gen/. Not sure if that's actually a bug in the debian tool chain.
| | 3 | No.3 Revision |
Handling of messages has changed in Fuerte. Message headers for C++ are installed in /opt/ros/fuerte/include/<package>, python files are installed in /opt/ros/fuerte/lib/python2.7/dist-packages/<package>/msg and lisp files in /opt/ros/fuerte/share/common-lisp/ros/<package>.
Generation of message files for actions are just a temporary step and the msg files themselves are normally not required for compiling ros packages. As far as I can see, they are installed at the moment into /opt/ros/fuerte/share/actionlib/tmp/buildd/ros-fuerte-actionlib-1.8.4-0oneiric-20120406-2119/obj-x86_64-linux-gnu/actions_gen/. Not sure if that's actually a bug in the debian tool chain.
If you need the msg files, I guess you can use the script genaction.py that comes with actionlib_msgs. E.g.:
rosrun actionlib_msgs genaction.py /path/to/action/Foo.action -o /path/for/generated/files
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.