ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
The --extend
option is define within catkin which generates the setup files (not catkin_tools
).
The chaining of workspaces basically works as follows:
What you can commonly not do is source two setup files. At least you won't get the result you might expect. Lets consider the following example:
Their are two options to get a "merged" environment:
--extend
.After describing all this for ROS 1 finally getting to the difference in ROS 2:
The setup files in ROS 2 / ament do not contain any logic to undo changes of previously sourced workspaces. Simply because that logic is very fragile and likely to be incomplete in non-trivial cases. As such they also don't provide the --extend
logic since you can simply source two setup files from independent workspaces and the result will be an environment containing both.