Replies: 3 comments
-
There is no support for recursively retrieving sources using I believe the idea is to use That does sort of require a If Colcon is not possible/available, two other approaches:
In both cases, the location of the repositories hosting the dependencies would be added to the I've used both approaches, the first one works pretty well, and avoids the download step when cleaning and rebuilding a workspace. The second approach is nice (from a minimal-package perspective), but does not solve the download problem. |
Beta Was this translation helpful? Give feedback.
-
Doesn't an external workspace solve these issue? I typically have two workspace for every project and external workspace where I put packages I normally do not touch and then the main workspace with the packages I am working on.
Here is how MoveIt CI does this. It basically loops over every package pulled from the primary rosinstall and then runs wstool merge on all the rosinstalls and to create a single rosinstall. Though it looks like some are starting to use vcstool instead of wstool which my have the functionality we need. |
Beta Was this translation helpful? Give feedback.
-
The official name for your "external workspace" is an underlay. And yes, that's what you would use an underlay for.
This is a custom bit of script (similar to the one I linked to on ROS Answers). Of course you could do something like this. The disadvantage of this approach however is it doesn't take care of any conflicts (ie: my dependency depends on something I also depend on, and now I have to source checkouts of the same thing ..). |
Beta Was this translation helpful? Give feedback.
-
This is a continuation of a discussion that started in PR #20 in tesseract_ros2..
To briefly summarize:
tesseract_ext
uses CMake'sAddExternalProject
function to clone and build Bullet, FCL, and some other packages. There might be a better way to approach this.package.xml
filedependencies.rosinstall
are not installed bywstool
when installing packages which include Tesseract in their own.rosinstall
file, so if Tesseract gains new dependencies then projects that use Tesseract need to add these dependencies on their own.wstool
andvcstool
, but I haven't had much success recursively evaluating source-repo dependencies).Beta Was this translation helpful? Give feedback.
All reactions