ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

How to overlay the correct way

asked 2020-04-20 07:12:25 -0600

madmax gravatar image

updated 2020-04-20 13:15:48 -0600

Let's say I want to overlay the rcl package.

Right now I have eloquent installed from deb packages.
So rcl lib is at /opt/ros/eloquent/lib/ .

Then I have an overlay workspace overlay_ws, where the rcl repo is checked out from source.
And a development workspace dev_ws.

I build overlway_ws first, then dev_ws.
And I source in this order:

  1. /opt/ros/eloquent/
  2. overlay_ws/
  3. dev_ws/

The sourcing happens in my .bashrc. So by opening a new terminal or calling an alias I can source the ros environment.

So first I source my environment, then build overlay_ws.
Then source the environment and build dev_ws.
Then source again, to have dev packages available.

But it always gets the installed lib (/opt/ros/..) linked and not the overlayed one.
If I remove the installed lib, it works. But that's not what I want.

Can someone hint me in the right direction?
Is this the way it should work?

edit retag flag offensive close merge delete


Could you clarify when you actually source any workspaces? Right now it's rather ambiguous whether you first build everything and only afterwards source, or whether you interleave those commands.

It would be important to know when you run which command.

gvdhoorn gravatar image gvdhoorn  ( 2020-04-20 07:18:37 -0600 )edit

Ok, updated my question.

madmax gravatar image madmax  ( 2020-04-20 09:09:23 -0600 )edit

If you start with overlays, I would suggest not to source anything in your .bashrc (at least initially). It will only confuse. Do it manually.

The correct order would be:

  • source /opt/ros/eloquent
  • build your overlay_ws (which is actually an underlay I would say)
  • source overlay_ws
  • build your dev_ws
  • source dev_ws

To source a workspace (or install location) essentially activates it. If you don't do that in the correct order, package paths will not be resolved to the correct workspace.

Having written this, I recall there are currently some issues with overlaying and ROS 2 workspaces, but I can't find the details right now.

Perhaps @marguedas can add something here.

gvdhoorn gravatar image gvdhoorn  ( 2020-04-20 09:14:06 -0600 )edit

If the dev_ws was not build before, the setup.bash is non existant and I can't source it anyway, which leads me to the next question. Do I need to build dev_ws from a clean state? Is it possible that a previous build cached some cmake linking paths or so? Then sourcing the overlay wouldn' have an effect at all.

madmax gravatar image madmax  ( 2020-04-20 11:28:24 -0600 )edit

Now I removed the installed as a test, tried to build dev_ws and it failed. So my custom rcl lib is not found although it's built. Then I removed the build folder of the failing package, built again and now it find's my lib. Looks like I need to clean the dev_ws completely.

madmax gravatar image madmax  ( 2020-04-20 11:51:42 -0600 )edit

@gvdhoorn maybe you're referring to this was a temporary issue that has now been solved.

The suggested workflow of not sourcing automatically before building and building + sourcing moving up the workspace chain looks good :+1: In my experience having dedicated (different) terminals for building and running code helps as wel

However what @madmax is trying to do is not a supported use case that I know of. Building packages already installed from debs in overlay is discouraged. It may work but may break in subtle ways. You'd need to at least make sure to rebuild every dependent of RCL (rclcpp, rclpy and any branch up your dependency tree from rcl) in your overlay and they should be before the debs ones on your various paths (AMENT_PREFIX_PATH, CMAKE_PREFIX_PATH, LD_LIBRARY_PATH, PATH etc) . Otherwise some libraries may still be pointing to the old rcl library ...(more)

marguedas gravatar image marguedas  ( 2020-04-20 11:52:07 -0600 )edit

Building packages already installed from debs in overlay is discouraged. -> this would be a good hint in the documentation. I do it like that because of the discussion here. And I hoped it would be enough to just build rcl and spdlog package. But after cleaning dev_ws and building again, it will always take the installed lib instead of the last sourced one.
I hoped the sourcing also does something like a library priorization, like on which path to look first for a library when building but that doesn't seem to be the case.
But after opening a new terminal, which resets all the PATH variables, and building dev_ws from there, the linking was correct.

madmax gravatar image madmax  ( 2020-04-20 13:14:49 -0600 )edit

Could you pls provide the ROS_PACKAGE_PATH and CMAKE_PREFIX_PATH after all your source operation?

tianb03 gravatar image tianb03  ( 2020-04-20 21:22:41 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2020-04-21 13:27:46 -0600

madmax gravatar image

So to sum it up:

I first cleaned my dev_ws and cleared the package and prefix path vars.
Then sourced and build the underlay of dev_ws.
Source the underlay and build overlay. Source overlay.

In my case I call a function which sources .bashrc and the workspaces in correct order.

export LD_LIBRARY_PATH=""                                                                                                                                                  
export AMENT_PREFIX_PATH=""                                                                                                                                                
export CMAKE_PREFIX_PATH=""                                                                                                                                                
source ~/.bashrc
edit flag offensive delete link more

Question Tools



Asked: 2020-04-20 07:12:25 -0600

Seen: 1,438 times

Last updated: Apr 21 '20