cmake-embedded

Name: cmake-embedded
Availability: InStock
Author: solitasroh

Automate embedded MCU build configuration with CMake and ARM toolchain setup.

2|1|Updated Mar 22, 2026

Search Tags:#embedded #cmake #stm32 #toolchain #arm-none-eabi #linker-script

Ready to run

npx skills add https://github.com/solitasroh/mcukit --skill cmake-embedded

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cmake-embedded
Source: https://github.com/solitasroh/mcukit/tree/main/skills/cmake-embedded
Command: npx skills add https://github.com/solitasroh/mcukit --skill cmake-embedded

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplifies and standardizes embedded MCU build configuration by providing a ready-to-use CMake-based workflow, including an ARM toolchain setup and linker-script integration, so firmware projects can be built consistently across environments.

Core Features & Use Cases

Centralized toolchain support for ARM Cortex-M devices (e.g., STM32, NXP Kinetis) with minimal setup.
Structured CMakeLists and build commands that enable deterministic cross-compilation and easy post-build artifacts generation.
Real-world use case: accelerate firmware bring-up by reusing a validated toolchain, build steps, and linker settings across multiple MCU projects.

Quick Start

Install the module, create a build directory, configure with cmake, and run the build to generate the firmware binary.

Frequently Asked Questions about cmake-embedded

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up CMake for STM32 cross-compilation?▼

Set up CMake for STM32 cross-compilation by applying a standardized CMake workflow with an ARM toolchain file. This provides a ready-to-use structure that configures the arm-none-eabi toolchain and integrates linker scripts for deterministic builds.

What's the best way to standardize embedded MCU build configuration across multiple projects?▼

The best way to standardize embedded MCU build configuration is using a centralized CMake workflow. It supplies a validated ARM toolchain setup and structured CMakeLists commands, ensuring firmware projects build consistently across different environments.

Does this CMake toolchain setup support NXP Kinetis microcontrollers?▼

Yes, the CMake toolchain setup supports NXP Kinetis microcontrollers. It provides centralized ARM Cortex-M device support with minimal setup, applying the same cross-compilation workflow and linker-script integration used for STM32 devices.

How do I integrate a linker script into an embedded CMake build?▼

Integrate a linker script into an embedded CMake build by utilizing the structured CMakeLists and build commands provided. This workflow ensures linker settings are correctly applied during cross-compilation to generate the final firmware binary.

Can I generate post-build artifacts like firmware binaries using CMake for ARM Cortex-M?▼

Yes, you can generate post-build artifacts using CMake for ARM Cortex-M. The workflow includes structured build commands that enable easy post-build artifacts generation alongside deterministic cross-compilation.

Why do I need a toolchain file for embedded CMake builds?▼

You need a toolchain file for embedded CMake builds to define the cross-compilation environment for the target MCU. It satisfies the requirement for arm-none-eabi toolchain setup, ensuring deterministic compilation for ARM Cortex-M devices.