Revision history [back]

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:

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

This is with catkin_make. For catkin_tools, you may use the --extend option to make the overlaying more explicit.

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

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.

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:

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

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

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

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.

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:

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

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).

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

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.

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:

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

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).

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.

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.