ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2012-09-08 18:40:47 -0500 | received badge | ● Famous Question (source) |
2012-09-08 18:40:47 -0500 | received badge | ● Popular Question (source) |
2012-09-08 18:40:47 -0500 | received badge | ● Notable Question (source) |
2011-06-19 22:20:49 -0500 | received badge | ● Scholar (source) |
2011-06-19 15:57:51 -0500 | received badge | ● Student (source) |
2011-06-19 10:29:41 -0500 | marked best answer | migrating to ros: duplicate package names ROS stack and package names are global to the entire ROS universe. It will be much less confusing and annoying to give all your stacks and packages unique names, like |
2011-06-19 10:29:26 -0500 | marked best answer | migrating to ros: duplicate package names I'm not sure, if that achieves what you want, but you can adjust your ROS_PACKAGE_PATH. If you include either RobotA or RobotB, the ros tools will only find the vision package in that stack. Using both at the same time under the same name is not possible. |
2011-06-18 14:54:39 -0500 | commented answer | migrating to ros: duplicate package names Thanks! I was afraid of that, but I'll just make a script that changes the package path. |
2011-06-18 12:49:29 -0500 | asked a question | migrating to ros: duplicate package names Hi all, I'm trying to migrate our robotics team's existing software, which uses a custom qmake-based build system, to ROS, but I'm running into a problem where packages have the same name, but are in different stacks. For Instance, we have unrelated code in: I've tried making RobotA and RobotB stacks, but then Thanks! |