-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose the QoS object wrapper #910
Conversation
Signed-off-by: Geoffrey Biggs <gbiggs@killbots.net>
Signed-off-by: Geoffrey Biggs <gbiggs@killbots.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for me with green CI.
Running CI |
Ups. I made mistake in gist. |
Something weird happening on CI. It looks like some problems with
This package present in Gist ros2.repos and it looks like that CI expecting to take it from |
Trying to rerun CI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gbiggs I see some linker errors on Windows platform https://ci.ros2.org/job/ci_windows/15821/console#console-section-13.
Could you please take a look on it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good though - take tidiness nitpick if you like
Signed-off-by: Geoffrey Biggs <gbiggs@killbots.net>
I changed the export to be on the class rather than the individual methods. @MichaelOrlov maybe this will fix those linker errors? I don't have any experience with Windows linking more recent than 20 years ago. |
@gbiggs I am also not an expert in Windows platform and don't have local install of the ROS build environment on Windows. |
The linker errors are still happening, but I can't figure out why. @emersonknapp do you have any ideas? |
…re it was exposed Signed-off-by: Emerson Knapp <eknapp@amazon.com>
I think it was from some outdated CMake workarounds, from before qos.hpp was exposed for use. The new visibility macros made it so that |
all PRs require green CI - don't need to use "request changes" for this
Gist: https://gist.githubusercontent.com/emersonknapp/ac55fdc23ec56ceadaeef4b401da616b/raw/a4b2a884c7a896a710454ad8a5d6a4df94fd0822/ros2.repos |
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Gist: https://gist.githubusercontent.com/emersonknapp/b7c9052c91d5e019c0bb348d3cbb28a8/raw/a4b2a884c7a896a710454ad8a5d6a4df94fd0822/ros2.repos |
This PR exposes the QoS wrapper in
rosbag_transport
for use by external users. This enables users of rosbag2 to create their ownrecorder
objects that mimic the behaviour of the providedRecorder
object with regards to QoS.