compulsorily sourcing multiple setup files in same shell.

asked 2015-12-09 22:22:20 -0600

creative_cimmons
47 ●5 ●10 ●12

updated 2015-12-09 22:23:06 -0600

Hello,

I have 2 catkin workspaces cata_ws , catb_ws

in cata_ws I have a.launch of nodea which when evoked would call b.launch which is in package nodeb in catb_ws.

my problem is if I do a rospack find ( in .launch I would do find) of nodeb , I get resource not found error.

The error is understandable because I have overwritten workspaces and currently cata_ws setup configuration is at the top.

So how do I successfully encode find of nodeb. I am working on a large project hence I need to compulsorily have separate workspaces.

Things I have tried and did not work.

set args=nodeb and value=pathtonodeb in a.launch . The problem is that in b.launch there are many includes to launches of other nodes in catb_ws
tried source [in cata_ws] devel/setup.sh --extends pathtocatb_ws/devel/setup.sh . Nope did not work

Thanks for the response.

answered 2015-12-10 01:51:00 -0600

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

updated 2015-12-10 06:58:50 -0600

Extending (or overlaying) a particular workspace is something that is most robustly done at build time, not afterwards.

The easiest way to get this working (assuming cata_ws overlays catb_ws) is to:

remove build and devel of both workspaces
start a new terminal and make sure to have only sourced whatever space catb_ws requires (ie: only the default Indigo setup.bash fi)
build catb_ws normally
source catb_ws/devel/setup.bash
now build cata_ws normally

If this is successful, you should now be able to (in a clean terminal fi) source cata_ws/devel/setup.bash and have rospack find pkg_in_catb_ws work.

This is with catkin_make. For catkin_tools, you may use the --extend option to config to make the overlaying more explicit (see catkin config – Configure a Workspace - Explicitly Specifying Workspace Chaining).

See also Overlaying with catkin workspaces and Overlaying multiple catkin devel-spaces at the same time. That last Q&A is slightly dated, but lists some nice-to-know gotchas.

edit flag offensive delete link

Comments

I'd add a step 6: source cata_ws/devel/setup.bash. Now both cata_ws and catb_ws will be "active" with cata_ws overlayed on catb_ws. The rospack command should be able to find packages in either workspace after only sourcing the cata_ws setup.bash file.