Sibling workspaces appear to be affecting build config

asked 2020-08-03 05:01:55 -0500

bgraysea gravatar image

As I understand; having multiple workspaces is possible. However; I think just the presence of "sibling" (so not nested) workspaces is affecting the build config.

I'm trying to mount the workspace for moveit tutorials; and ideally two other workspaces I have been creating myself.

"blah" only has ws_moveit

~/blah$ ls -lrt
total 4
drwxrwxr-x 7 brent brent 4096 ago  3 10:42 ws_moveit

"catkin_wses" has three workspaces

ls -lrt
total 12
drwxrwxr-x 4 brent brent 4096 ago  3 08:43 ws_ada500
drwxrwxr-x 3 brent brent 4096 ago  3 08:44 ws_moveit
drwxrwxr-x 3 brent brent 4096 ago  3 08:47 ws_nene

When I start the docker container with docker run -it -v ~/blah:/root melodic-desktop-full-c-1 the output of catkin config --extend /opt/ros/${ROS_DISTRO} --cmake-args -DCMAKE_BUILD_TYPE=Release includes

Workspace: /root/ws_moveit which is expected

However; mounting in the folder with three workspaces via docker run -it -v ~/catkin_wses:/root melodic-desktop-full-c-1 then gives Workspace: /root (ws_moveit is missing) although I am running from the exact same directory ~/ws_movei

Do I need to do something specific to support having multiple folders which each have their own workspace in them?

edit retag flag offensive close merge delete