Open aosmw opened 3 weeks ago
Indeed, for now, non-upstream dependencies are not working with in-container
. Being able to pass .deb file could be a solution.
For build-in-container
and test-in-container
the source of the dependency can be passed to satisfy the dependency.
Since the packages are processed in order, maybe we could come up with a --install-deb
flag or such that would install the newly generated deb package before moving on to the next one.
The actual error was due to a cmake check where Fields2cover tests for a function provided by a newly packaged ortools_vendor.
Manually installing the ortools_vendor package with dpkg -i /ws/release/ortools_vendor/ros-humble-ortools-vendor_9.9.0-0jammy_amd64.deb
and then manually restarting the Fields2cover build showed that it satisfied the dependency.
Maybe there is a way to inject the /ws/release directory into the places searched by rosdep.