Conflicts between Cartographer and other packages

[duffrea]

Hi, sorry to bother you again but I have problems after making catkin_make_isolated --install.

Starting from the beginning, I had problems when performing catkin_make_isolated --install --use -ninja, but I removed the --use -ninja part as you suggested in an another issue, and I solved the problem.

Unfortunately I encountered other problems when I tried to add other packages to the workspace.

In particular, even if performing catkin_make_isolated --install and source install_isolated/setup.bash with the added packages doesn't give any error, the trouble comes when I try to launch launch files belonging to the packages that I added.
This is a template of the error:

RLException: [scout.launch] is neither a launch file in package [gazebo] nor is [gazebo] a launch file name
The traceback for the exception was written to the log file

In my opinion this happens because the added packages are not sourced properly, but in order to make Cartographer work source install_isolated/setup.bash is mandatory and I don't know how to solve this problem, and, as a consequence I don't know how to integrate my packages with the functionalities provided by Cartographer. I also tried to use catkin build instead of catkin_make_isolated --install, but I had some strange errors when building cartographer_ros.

If you have any suggestions, I would be grateful.

Thanks in advance.

[ojura]

Hi! Packages for the scout are sometimes not friendly for building in isolation. I would suggest you use catkin_make for them and then build this separately - you can layer Catkin workspaces on top of each other; all that is important is what the environment is when you are building a repo.

E.g. when you build any workspace, you usually layer in on top of the /opt/ros install workspace by having that source'd. But you can have some other workspace ws1 instead, and the final result will be layered on top of it (meaning that in ws2, you will see everything from /opt/ros, ws1 and ws2).