Closed berndpfrommer closed 2 years ago
I don't know for sure, but something stood out about your sourcing:
. /opt/ros/noetic/setup.bash
. /opt/ros/foxy/local_setup.bash
. ~/Documents/my_ros1_overlay/devel/setup.bash # to get ros1 custom message definition
. ~/Documents/my_ros2_overlay/install/local_setup.bash # to get ros2 custom message definition
You should only need to source your individual workspace, if it was built against the /opt/ros
installation, in both cases, e.g.
source my_ros1_overlay/devel/setup.bash
source my_ros2_overlay/install/setup.bash
It's probably fine, since you were using local_setup.bash
(only sources the specific workspace) instead of setup.bash
(sources workspace and its parent chaine.g. /opt/ros
)
The usage for rosbag2_bag_v2
says you must source ROS 1 then ROS 2 - in your setup there you are mixing the order by sourcing 1,2,1,2. Can you try either the above 2-step source, or 1,1,2,2, and see if that works for you?
Thanks for the response! Traveling right now with no access to the robot for several more weeks. Will try different sourcing next time I get a chance.
I dropped the ball on this one. I upgraded to Galactic before trying your suggestion. As far as I am concerned this issue can be closed for now as I will not be able to reproduce it going forward.
I'm getting this error when trying to build the ROS bridge for custom messages. This is on Ubuntu 20.04, with ROS1 noetic and ROS2 foxy installed in parallel from the standard Ubuntu 20.04 packages:
Then checkout the "foxy" branch of the ros1_bridge into separate workspace and build it:
The only way I can get it to build is by removing the theora image transport by inserting this on line 92 of
ros1_bridge/CMakeLists.txt
: