Is there a way to build packages "up-to" by passing a directory path?
Let's say I have a workspace with:
And i want to only colcon build my-package-to-compile and all its dependencies. This is a simple example, but I have a workspace with over 50 packages/meta-packages. Now, I list the packages that are no in the deps directory and use --packages-up-to with the list i created. I am testing now with ros1 by the way.
Is there a way to do that without this "hack"?
Thanks
Just to clarify: You want to build a set of
Npackages including its dependencies out of a workspace withMpackages, where you put some dependencies (in whatever way you identify those) into adepssubdirectory containing anotherLpackages?Yes exactly, thanks. I put all the dependencies in one directory and the core packages in another. Now I'd like to tell colcon to build all core ones and dependencies and ignore all non needed dependencies. Now, I'm doing a "hack" with rospack list and depends to get exactly what I need but it's not clean
I don't think (but I don't know) if there is something like this available. This would be a complete new feature, I guess.
If you always build ALL core packages, and all dependencies (but no other packages) are in the
depsdirectory, I don't think there is a difference between calling colcon without a package or with all core packages. Packages that haven't changed will not be built anyways (even though CMake configuration might run).If the list of packages you want to build is not changing, or not changing a lot, I'd actually go for a bash alias..
Maybe, to avoid an xy-problem here, you could clarify a bit more why you need to do it this way? I.e., what do you expect to gain from this approach?
Thanks for the link. I didn't know there was a name for this! The end goal is to create different bundles with colcon bundle, in jenkins and save time. Each of my 15 repositories contains one metapackage and between 2 and 10 packages, so if one depends on another which depends on another... I can end up with a workspace of 30 packages easily, but the packages i bundle only can require 5 for example. Since i need to bundle around 10 packages (now, it will be more later on), the resulting time difference is very high
But how does the approach of putting dependencies (I read this now as repos) in a sub-directory solve your issues? This means that you basically have a configuration somehow where you need to put what. I.e. you put some repos in the workspace root, some in the deps folder. But when you have that config, can't you just directly take this configuration for creating the build?
Thanks, I see what you mean, I will try to simplify over the weekend and come back.