ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
a) There is (as far as I know) no program or tool to automate the migration.
b) I migrated all of my packages and I did not find it too difficult. In the C++/Phython/ msg/srv-files usually you do not have to make any changes. Only you have to create a package.xml in lieu of manifest.xml and change the CMakeLists.txt according to the /catkin/migrating_from_rosbuild you mentioned. This has to be done for each package, though. But the structure of your packages in your workspace you can very much keep below the catkin_ws/src and the dependency structure also very much stays the same.
2 | No.2 Revision |
a) There is (as far as I know) no program or tool to automate the migration.
b) I migrated all of my packages and I did not find it too difficult. In the C++/Phython/ msg/srv-files usually you do not have to make any changes. Only you have to create a package.xml in lieu of manifest.xml and change the CMakeLists.txt according to the /catkin/migrating_from_rosbuild you mentioned. This has to be done for each package, though. But the structure of your packages in your workspace you can very much keep below the catkin_ws/src and the dependency structure also very much stays the same.
I can not help you with the multiple kinect part of your question. I think you might better open a separate question on this;)