Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

error: field 'platform' has incomplete type

Open
#713 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c

Research direction

Start with firmware/mcu_ws/eProsima/Micro-XRCE-DDS-Client/include/uxr/client/profile/transport/serial/serial_transport.h and inspect the build output and attached screenshots for the missing uxrSerialPlatform definition. Reproduce the custom ROS message tutorial on the STM32F722ZET6U with FreeRTOS, then identify the configuration or include issue that causes the incomplete-type error. Done means the micro-ROS workspace builds successfully.

Written by the indexing model from the issue text.

Description

Issue template

  • Hardware description: STM32F722ZET6U
  • RTOS: FreeRTOS
  • Installation type: custom ROS message
  • Version or commit hash: Humble
Steps to reproduce the issue

I'm a beginner doing tutorials on the "micro.ros.org " site.
Among them, an error occurs during the "How to include a custom ROS message in micro-ROS" process and asks questions.
An error occurs while building micro-ROS workspace, and it does not work.
I'd appreciate your help.

Actual behavior

The error contents are as follows.

firmware/mcu_ws/eProsima/Micro-XRCE-DDS-Client/include/uxr/client/profile/transport/serial/serial_transport.h:39:30: error: field 'platform' has incomplete type
struct uxrSerialPlatform platform;
^~~~~~~~

Additional information

I attach the details as a picture.

1
2
3
4
5
7
8
9
10
11

Dominant language
Shell
Stars
509
Forks
183
Avg merge
22h 26m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from micro-ROS/micro_ros_setup

All issues in micro-ROS/micro_ros_setup

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.