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 |
In ROS Fuerte, some of the core stacks/packages were converted to use a prototype version of the catkin buildsystem (docs here). In this version, the notions of "packages" and "stacks" were re-defined (all deps were pushed to the stack level and all manifest.xml files were removed). Since common_msgs is one of these stacks that was catkinized, neither rospack nor rosstack in Fuerte can parse this xml file. You'll see that things like dependency specification are defined differently:
ROS Diamondback (rosbuild)
<depend stack="ros_comm" /><depend package="rosbagmigration"/> (gives you std_msgs via this dep)ROS Fuerte (catkin prototype):
<build_depends>std_msgs</build_depends>, <depends>std_msgs</depends>ROS Groovy (new catkin):
<build_depend>std_msgs</build_depend>, <run_depend>std_msgs</run_depend>| | 2 | No.2 Revision |
In ROS Fuerte, some of the core stacks/packages were converted to use a prototype version of the catkin buildsystem (docs here). In this version, the notions of "packages" and "stacks" were re-defined (all deps were pushed to the stack level and all manifest.xml files were removed). Since common_msgs is one of these stacks that was catkinized, neither rospack nor rosstack in Fuerte can parse this xml file. You'll see that things like dependency specification are defined differently:
ROS Diamondback (rosbuild)(rosbuild)
<depend stack="ros_comm" /><depend package="rosbagmigration"/> (gives you std_msgs via this dep)ROS Fuerte (catkin prototype):(catkin prototype):
<build_depends>std_msgs</build_depends>, <depends>std_msgs</depends>ROS Groovy (new catkin):(new catkin):
<build_depend>std_msgs</build_depend>, <run_depend>std_msgs</run_depend>| | 3 | No.3 Revision |
In ROS Fuerte, some of the core stacks/packages were converted to use a prototype version of the catkin buildsystem (docs here). In this version, the notions of "packages" and "stacks" were re-defined (all deps were pushed to the stack level and all manifest.xml files were removed). made to just contain other metadata). Since common_msgs is one of these stacks that was catkinized, neither rospack nor rosstack in Fuerte can parse this xml file. You'll see that things like dependency specification are defined differently:
ROS Diamondback (rosbuild)
<depend stack="ros_comm" /><depend package="rosbagmigration"/> (gives you std_msgs via this dep)ROS Fuerte (catkin prototype):
<build_depends>std_msgs</build_depends>, <depends>std_msgs</depends>ROS Groovy (new catkin):
<build_depend>std_msgs</build_depend>, <run_depend>std_msgs</run_depend>| | 4 | No.4 Revision |
In ROS Fuerte, some of the core stacks/packages were converted to use a prototype version of the catkin buildsystem (docs here). In this version, the notions of "packages" and "stacks" were re-defined (all deps were pushed to the stack level and all manifest.xml files were made to just contain other metadata). Since common_msgs is one of these stacks that was catkinized, neither rospack nor rosstack in Fuerte can parse this xml file. In this case, std_msgs gets built and installed top /opt/ros/fuerte/include/std_msgs (the new FHS standard), so as long as /opt/ros/fuerte is in a given C++ package's include path, you will be able to include C++ headers from std_msgs (there's a similar setup for Python). You'll see that things like dependency specification are defined differently:
ROS Diamondback (rosbuild)
<depend stack="ros_comm" /><depend package="rosbagmigration"/> (gives you std_msgs via this dep)ROS Fuerte (catkin prototype):
<build_depends>std_msgs</build_depends>, <depends>std_msgs</depends>ROS Groovy (new catkin):
<build_depend>std_msgs</build_depend>, <run_depend>std_msgs</run_depend>| | 5 | No.5 Revision |
In ROS Fuerte, some of the core stacks/packages were converted to use a prototype version of the catkin buildsystem (docs here). In this version, the notions of "packages" and "stacks" were re-defined (all deps were pushed to the stack level and all manifest.xml files were made to just contain other metadata). Since common_msgs is one of these stacks that was catkinized, neither rospack nor rosstack in Fuerte can parse this xml file. In this case, std_msgs gets built and installed top /opt/ros/fuerte/include/std_msgs (the new FHS standard), so as long as /opt/ros/fuerte is in a given C++ package's include path, you will be able to include C++ headers from std_msgs (there's a similar setup for Python). You'll see that things like dependency specification are defined differently:
ROS Diamondback (rosbuild)
<depend stack="ros_comm" /><depend package="rosbagmigration"/> (gives you std_msgs via this dep)ROS Fuerte (catkin prototype):
<build_depends>std_msgs</build_depends>, <depends>std_msgs</depends>ROS Groovy (new catkin):
<build_depend>std_msgs</build_depend>, <run_depend>std_msgs</run_depend>
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.