Handling conflicting ROS package versions: Need guidance
Hi all,
I'm encountering a dependency conflict with my ROS package, baggie
. It requires rosbag2_cpp
, rosbag2_compression
, and rosbag2_storage
. However, the standard rosbag2
in ROS 2 Foxy lacks some essential features I need. So, I built the rosbag2
package from source (foxy_future
branch) to address this. Unfortunately, it interferes with the standard rosbag2
, causing baggie
to fail during runtime.
How can I instruct baggie
to use the standard rosbag2
version while allowing the other packages to utilize the newer version I built?
Ideally, I would like to have all the packages within the same workspace for better git control and ease of building. However, despite several days of effort, I am open to having them in different workspaces. In that case, it would be extremely helpful if I could source them simultaneously to simplify my workflow.
Appreciate any help or suggestions. Let me know if you need more information. Thanks!
Platform:
- OS: Ubuntu 20.04
- ROS version: ROS 2 Foxy
Asked by Sahas_Ananth on 2023-07-08 13:44:21 UTC
Answers
Change the package names (in the package.xlm and CMakeList), and then use that "custom" package name in the CMakeList for the package that you need those features.
Asked by MSanMon on 2023-07-10 15:37:53 UTC
Comments