You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have ROS2 Foxy build from source, and everything works fine there.
I created a new workspace for rosbag2, as suggested in the readme.
I cloned foxy-future and tried to build the package with colcon build --merge-instal
I did the same with the master branch too
Expected Behavior
I expected the packaged to be built, so I can use the python-API for rosbag2
Actual Behavior
The build failed on rosbag2_storage (see additional context)
To Reproduce
** Steps to reproduce the behavior, e.g.
git clone rosbag2 from foxy-future or master
colcon build --merge-install
System (please complete the following information)
master is the Rolling / Galactic source branch - it is not expected to build against a Foxy installation. Additionally - foxy-future is not yet implemented, if you would like to try building it now, please check out the branch from the PR #687
So - this behavior is currently as expected - I will close this ticket.
Hello all,
after git checkout foxy-future, build OK. So, how to use let ros2 bag play [ros2_bag] play the /clock topic.
My OS is ubuntu20.04, installed foxy by debian. I want to play ros2 bag offline to test a slam and localization system. /clock topic is not published by anyone.
Description
I have ROS2 Foxy build from source, and everything works fine there.
I created a new workspace for rosbag2, as suggested in the readme.
I cloned foxy-future and tried to build the package with colcon build --merge-instal
I did the same with the master branch too
Expected Behavior
I expected the packaged to be built, so I can use the python-API for rosbag2
Actual Behavior
The build failed on rosbag2_storage (see additional context)
To Reproduce
** Steps to reproduce the behavior, e.g.
System (please complete the following information)
Additional context
The text was updated successfully, but these errors were encountered: