apps/system/microros: add empty library skeleton#3492
Merged
Conversation
Contributor
|
@arjav1528 could you add CMake support too? |
Add Make.defs with copyright header for the micro-ROS library build system. This establishes the directory structure for Phase 2, with actual build logic to follow in subsequent steps. Signed-off-by: Arjav Patel <arjav1528@gmail.com>
Add Kconfig file defining CONFIG_SYSTEM_MICROROS and related options: - MICROROS_DISTRO: ROS 2 distribution selection (default jazzy) - MICROROS_TRANSPORT_UDP/SERIAL: Transport method selection - MICROROS_AGENT_IP/PORT: UDP agent address configuration - MICROROS_SERIAL_DEVICE/BAUD: Serial transport configuration - Resource limits: MAX_NODES, MAX_PUBLISHERS, MAX_SUBSCRIPTIONS, MAX_SERVICES, MAX_CLIENTS Allows menuconfig integration for micro-ROS library configuration. Signed-off-by: Arjav Patel <arjav1528@gmail.com>
Add Makefile with standard NuttX build system integration. Follows the MENUDESC + Directory.mk pattern used throughout nuttx-apps. Enables the system/microros module to be built as part of the apps directory build process. Signed-off-by: Arjav Patel <arjav1528@gmail.com>
Ignore build outputs and generated files: - Directories: micro_ros_src/, micro_ros_dev/, build/, install/ - Build outputs: libmicroros.a, toolchain.cmake, colcon.meta - Archives: *.tar.gz Prevents build artifacts and downloaded sources from being committed. Signed-off-by: Arjav Patel <arjav1528@gmail.com>
147db1f to
16b3ba3
Compare
Add CMakeLists.txt file for CMake build system integration. Enables the micro-ROS library module to be built using NuttX CMake build system alongside traditional Make-based builds. Signed-off-by: Arjav Patel <arjav1528@gmail.com>
Contributor
Author
done, added |
xiaoxiang781216
approved these changes
May 21, 2026
jerpelea
approved these changes
May 21, 2026
acassis
approved these changes
May 21, 2026
Contributor
|
@arjav1528 very nice! Please create a documentation inside repository nuttx/Documentation/ |
Contributor
Author
sure, will do, but like I am planning to do the documentation in my last and final PR, like after completing all the integration |
lupyuen
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: Please adhere to Contributing Guidelines.
Summary
Establish the directory structure and build system integration for micro-ROS
library in NuttX apps. This PR adds the foundational skeleton for Phase 2 of
the micro-ROS integration project—Kconfig with full configuration options for
ROS 2 distribution selection, transport layer choice (UDP/serial), agent
addressing, and resource limits. Makefile follows standard NuttX pattern using
MENUDESC and Directory.mk.
Impact
Build System:
apps/system/microros/as new system moduleMake.defswildcard includemkkconfig.shKconfig generationConfiguration:
MICROROS_MAX_SERVICES, MICROROS_MAX_CLIENTS: resource limits
Testing
Host Environment:
Target Verification:
Test Procedure: