Viability of using RCLCPP as the client library for low resource arm based linux systems

Nobody has claimed this yet.

- Hardware description: NI Roborio (armv7 softfp, with 256mb ram)
- RTOS: linux kernel with real-time scheduler patch
- Installation type: micro_ros_setup to build static library for platform
- Version or commit hash: galactic

Hi, I have a question about the viability of using RCLCPP in place of RCLC for low power / resource constrained arm systems. So far I have a working version of micro_ros for the platform, as well as a working colcon.meta and toolchain, but was curious if it would be possible to use RCLCPP as the client library for the micro_ros client. Given our use case is already C++ on the device, using RCLCPP seems to be a better fit. Especially rather than than having to write a significant wrapper around RCLC. Would this switch even be possible, or are the two client libraries functionally different enough to a point where it would not work? Thank you for your help! (Sorry if this is the wrong place to pose this question)

Review the micro_ros_setup Galactic build configuration, including the reported colcon.meta and toolchain, and compare how RCLCPP and RCLC are supported for the NI Roborio armv7 softfp target. The issue names no source files or tests; done would require a clear feasibility determination and an identified implementation or configuration path.

Written by the indexing model from the issue text.