Provide branch for ROS 2 Jazzy and update GIT_TAG for xrceagent

未关闭
#223 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
cpp

调研方向

从 rolling 分支中的 SuperBuild.cmake 开始,检查 Micro-XRCE-DDS-Agent 的 GIT_TAG。source ROS Rolling 后重现 colcon build,然后检查 graph_typesupport.cpp 以及所引用的 prs/pr-rolling-fastcdr-2.2.x 分支中的补丁。完成的标准是 agent 能够针对所请求的 ROS 2 分支使用 Fast-CDR 2.2.x 构建。

由索引模型根据 Issue 内容生成。

描述

Issue template

This is a feature request. ROS 2 Rolling and Jazzy depend on Fast-CDR 2.2.x. Version 2.4.3 of Micro-XRCE-DDS-Agent supports this but the GIT_TAG in the SuperBuild.cmake in the rolling branch refers to ros2

Steps to reproduce the issue
  • Create a colcon workspace to build this repo, and source ROS Rolling before building.
Expected behavior
  • micro-ROS-Agent will build in a colcon workspace that has sourced ROS Rolling.
Actual behavior
  • micro-ROS-Agent will not build in a colcon workspace that has sourced ROS Rolling.
Additional information

Looks like this will require code changes as well, as micro-ROS-agent will not build against the updated Fast-CDR version. For example:

/Users/rhys/Code/ros2/rolling/ros2-ardupilot/src/micro_ros_agent/micro_ros_agent/src/agent/graph_manager/graph_typesupport.cpp:57:33: error: no member named 'DDS_CDR' in 'eprosima::fastcdr::Cdr'
        eprosima::fastcdr::Cdr::DDS_CDR);
        ~~~~~~~~~~~~~~~~~~~~~~~~^
/Users/rhys/Code/ros2/rolling/ros2-ardupilot/src/micro_ros_agent/micro_ros_agent/src/agent/graph_manager/graph_typesupport.cpp:64:54: error: no member named 'getSerializedDataLength' in 'eprosima::fastcdr::Cdr'; did you mean 'get_serialized_data_length'?
        payload->length = static_cast<uint32_t>(scdr.getSerializedDataLength());
                                                     ^~~~~~~~~~~~~~~~~~~~~~~
                                                     get_serialized_data_length
/Users/rhys/Code/ros2/rolling/ros2-rolling/install/fastcdr/include/fastcdr/Cdr.h:266:23: note: 'get_serialized_data_length' declared here
    Cdr_DllAPI size_t get_serialized_data_length() const;
                      ^
/Users/rhys/Code/ros2/rolling/ros2-ardupilot/src/micro_ros_agent/micro_ros_agent/src/agent/graph_manager/graph_typesupport.cpp:80:33: error: no member named 'DDS_CDR' in 'eprosima::fastcdr::Cdr'
        eprosima::fastcdr::Cdr::DDS_CDR);
        ~~~~~~~~~~~~~~~~~~~~~~~~^
/Users/rhys/Code/ros2/rolling/ros2-ardupilot/src/micro_ros_agent/micro_ros_agent/src/agent/graph_manager/graph_typesupport.cpp:149:33: error: no member named 'DDS_CDR' in 'eprosima::fastcdr::Cdr'
        eprosima::fastcdr::Cdr::DDS_CDR);
        ~~~~~~~~~~~~~~~~~~~~~~~~^
/Users/rhys/Code/ros2/rolling/ros2-ardupilot/src/micro_ros_agent/micro_ros_agent/src/agent/graph_manager/graph_typesupport.cpp:156:54: error: no member named 'getSerializedDataLength' in 'eprosima::fastcdr::Cdr'; did you mean 'get_serialized_data_length'?
        payload->length = static_cast<uint32_t>(scdr.getSerializedDataLength());
                                                     ^~~~~~~~~~~~~~~~~~~~~~~
                                                     get_serialized_data_length
/Users/rhys/Code/ros2/rolling/ros2-rolling/install/fastcdr/include/fastcdr/Cdr.h:266:23: note: 'get_serialized_data_length' declared here
    Cdr_DllAPI size_t get_serialized_data_length() const;
                      ^
/Users/rhys/Code/ros2/rolling/ros2-ardupilot/src/micro_ros_agent/micro_ros_agent/src/agent/graph_manager/graph_typesupport.cpp:172:33: error: no member named 'DDS_CDR' in 'eprosima::fastcdr::Cdr'
        eprosima::fastcdr::Cdr::DDS_CDR);
        ~~~~~~~~~~~~~~~~~~~~~~~~^
6 errors generated.
make[2]: *** [CMakeFiles/micro_ros_agent.dir/src/agent/graph_manager/graph_typesupport.cpp.o] Error 1
make[1]: *** [CMakeFiles/micro_ros_agent.dir/all] Error 2

This branch contains patches to fix the above issue: https://github.com/srmainwaring/micro-ROS-Agent/tree/prs/pr-rolling-fastcdr-2.2.x

主要语言
C++
星标
201
派生
111
平均合并
1 天 6 小时
30 天内合并 PR
10

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

micro-ROS/micro-ROS-Agent 的其他 Issue

查看 micro-ROS/micro-ROS-Agent 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。