C++ API : concept for typesupport #199
Conversation
Signed-off-by: Jan Staschulat <jan.staschulat@de.bosch.com>
|
@pablogs9 interestingly, the same build error ( |
Codecov Report
@@ Coverage Diff @@
## master #199 +/- ##
=======================================
Coverage 60.95% 60.95%
=======================================
Files 13 13
Lines 1493 1493
Branches 445 445
=======================================
Hits 910 910
Misses 377 377
Partials 206 206 Continue to review full report at Codecov.
|
| //const rosidl_message_type_support_t * ping_type_support = | ||
| // ROSIDL_GET_MSG_TYPE_SUPPORT(std_msgs, msg, String); | ||
| const rosidl_message_type_support_t ping_type_support = | ||
| rclcpp::get_message_type_support_handle< std_msgs::msg::String >(); |
There was a problem hiding this comment.
Will we need rclcpp to build rclc examples?
There was a problem hiding this comment.
At the moment yes. But his is not the intention.
This was a first idea for the typesupport conversion. First, I wanted to understand, which functions are necessary to write a subscriber with callback function in C++ so that it is compatible with rclc library.The idea is to factor out the necessary rclcpp functions - so that we don't have the dependency of rclcpp.
I converted this pull request to Draft.
JanStaschulat
changed the title
Example with ROS 2 message type support (definition of subscription and callback function).