Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

rt-claw-build

Estrelas5

Forks0

Atualizado13 de maio de 2026 às 16:42

Use when building rt-claw, choosing a platform target, running QEMU, flashing hardware, or debugging C/Meson/native build failures.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

gevico

gevico/rt-claw

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name	rt-claw-build
description	Use when building rt-claw, choosing a platform target, running QEMU, flashing hardware, or debugging C/Meson/native build failures.
license	MIT

rt-claw Build

Use the repository Makefile before inventing ad hoc commands. Meson builds the platform-independent libraries; each platform target then uses its native build system when needed.

Quick Commands

Task	Command
Linux native build	`make build-linux`
Linux native run	`make run-linux`
Unit tests on Linux	`make test-unit-linux`
ESP32-C3 QEMU build	`make build-esp32c3-qemu`
ESP32-C3 QEMU run	`make run-esp32c3-qemu`
ESP32-C3 devkit build	`make build-esp32c3-devkit`
ESP32-C3 xiaozhi-xmini build	`make build-esp32c3-xiaozhi-xmini`
ESP32-C3 xiaozhi-xmini flash	`make flash-esp32c3-xiaozhi-xmini`
ESP32-S3 QEMU build	`make build-esp32s3-qemu`
ESP32-S3 hardware build	`make build-esp32s3`
ESP32-S3 hardware flash	`make flash-esp32s3`
vexpress-a9 QEMU build	`make vexpress-a9-qemu`
Zynq-A9 QEMU build	`make build-zynq-a9-qemu`
Zephyr Cortex-M3 QEMU build	`make build-zephyr-cortex-m3-qemu`
Zephyr Cortex-A9 QEMU build	`make build-zephyr-cortex-a9-qemu`
Style check	`scripts/check-patch.sh --staged`

Run Options

Pass GDB=1 to QEMU run targets to start in debug mode on port 1234.
Pass GRAPHICS=1 to ESP32 QEMU run targets when an LCD window is needed.
Real hardware targets require the board to be connected before flash or monitor commands run.

Target Selection

Use the platform named by the user.
If no platform is named, inspect changed paths:
- platform/linux/, osal/linux/, or unit tests -> make build-linux
- platform/esp32c3/ or Espressif C3 drivers -> make build-esp32c3-qemu
- platform/esp32s3/ or shared Espressif changes -> make build-esp32s3-qemu
- platform/vexpress-a9/ or osal/rtthread/ -> make vexpress-a9-qemu
- platform/zynq-a9/ or osal/freertos/ -> make build-zynq-a9-qemu
- platform/zephyr/ or osal/zephyr/ -> a Zephyr QEMU build target
Check branch names for platform hints such as esp32c3, esp32s3, vexpress, zynq, or zephyr.
If ambiguous, use make build-linux for the fastest compile check.

Workflow

Confirm branch and worktree with git status -sb.
Read CLAUDE.md for current platform commands before changing a command.
Run the narrowest useful build while iterating.
Run scripts/check-patch.sh --staged before committing staged C changes.
For PR submission, build at least one affected platform. Broaden to more platforms when changing shared claw/, include/, osal/, drivers/, or build-system files.

Failure Handling

Preserve the first compiler or linker error; later failures may be follow-on noise.
Report style failures from scripts/check-patch.sh --staged, but do not hide the build result behind style output.
Check Meson source lists when a symbol is undefined or a new file is not compiled.
Check include order and OSAL boundaries before adding headers.
Do not edit unrelated platforms just because a matrix build visits them.
Keep build/ artifacts out of commits.

Mais deste repositório

mesmo repositório

rt-claw-ci-coverage

gevico/rt-claw

Use when adding CI coverage for a new rt-claw module, feature chain, endpoint backend, service integration, or regression.

2026-05-145

rt-claw-code-explorer

gevico/rt-claw

Use when finding rt-claw definitions, call sites, subsystem ownership, build wiring, OSAL boundaries, or platform-specific implementations.

2026-05-135

rt-claw-diagnose

gevico/rt-claw

Use when analyzing rt-claw build logs, QEMU output, serial monitor logs, CI failures, network/API failures, or boot/runtime crashes.

2026-05-135

rt-claw-docs-sync

gevico/rt-claw

Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization.

2026-05-135

rt-claw-new-module

gevico/rt-claw

Use when adding a new rt-claw service, driver, tool, platform helper, platform port, or RTOS backend.

2026-05-135

rt-claw-osal-review

gevico/rt-claw

Use when reviewing rt-claw changes for OSAL boundary violations, RTOS coupling, platform leakage, driver layering, or portability risks.

2026-05-135

rt-claw Build

Use the repository Makefile before inventing ad hoc commands. Meson builds the platform-independent libraries; each platform target then uses its native build system when needed.

Quick Commands

Task

Command

Linux native build

make build-linux

Linux native run

make run-linux

Unit tests on Linux

make test-unit-linux

ESP32-C3 QEMU build

make build-esp32c3-qemu

ESP32-C3 QEMU run

make run-esp32c3-qemu

ESP32-C3 devkit build

make build-esp32c3-devkit

ESP32-C3 xiaozhi-xmini build

make build-esp32c3-xiaozhi-xmini

ESP32-C3 xiaozhi-xmini flash

make flash-esp32c3-xiaozhi-xmini

ESP32-S3 QEMU build

make build-esp32s3-qemu

ESP32-S3 hardware build

make build-esp32s3

ESP32-S3 hardware flash

make flash-esp32s3

vexpress-a9 QEMU build

make vexpress-a9-qemu

Zynq-A9 QEMU build

make build-zynq-a9-qemu

Zephyr Cortex-M3 QEMU build

make build-zephyr-cortex-m3-qemu

Zephyr Cortex-A9 QEMU build

make build-zephyr-cortex-a9-qemu

Style check

scripts/check-patch.sh --staged

Run Options

Pass GDB=1 to QEMU run targets to start in debug mode on port 1234.

Pass GRAPHICS=1 to ESP32 QEMU run targets when an LCD window is needed.

Real hardware targets require the board to be connected before flash or monitor commands run.

Target Selection

Use the platform named by the user.

If no platform is named, inspect changed paths:

platform/linux/, osal/linux/, or unit tests -> make build-linux
platform/esp32c3/ or Espressif C3 drivers -> make build-esp32c3-qemu
platform/esp32s3/ or shared Espressif changes -> make build-esp32s3-qemu
platform/vexpress-a9/ or osal/rtthread/ -> make vexpress-a9-qemu
platform/zynq-a9/ or osal/freertos/ -> make build-zynq-a9-qemu
platform/zephyr/ or osal/zephyr/ -> a Zephyr QEMU build target

Check branch names for platform hints such as esp32c3, esp32s3, vexpress, zynq, or zephyr.

If ambiguous, use make build-linux for the fastest compile check.

Workflow

Confirm branch and worktree with git status -sb.

Read CLAUDE.md for current platform commands before changing a command.

Run the narrowest useful build while iterating.

Run scripts/check-patch.sh --staged before committing staged C changes.

For PR submission, build at least one affected platform. Broaden to more platforms when changing shared claw/, include/, osal/, drivers/, or build-system files.

Failure Handling

Preserve the first compiler or linker error; later failures may be follow-on noise.

Report style failures from scripts/check-patch.sh --staged, but do not hide the build result behind style output.

Check Meson source lists when a symbol is undefined or a new file is not compiled.

Check include order and OSAL boundaries before adding headers.

Do not edit unrelated platforms just because a matrix build visits them.

Keep build/ artifacts out of commits.