メニュー
Use for configuring, reusing, building, or diagnosing QEMU build directories. Defaults to build and keeps agent-created logs and reports under a .oh-my-qemu task workspace.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use as the first step for any non-trivial QEMU task. Produces a small implementation or debugging plan under a .oh-my-qemu task workspace with acceptance criteria, scope boundaries, artifact policy, and verification gates.
Use for QEMU board, SoC, machine, memory map, boot path, FDT/ACPI, and IRQ topology modeling. Extends qemu-plan and qemu-rlcr-loop; board work must add or extend qemu-qtest coverage for verification.
Use for booting Linux in QEMU through either direct kernel loading or firmware and bootloader stages, selecting the path from task inputs while preserving provenance, boot logs, debug handoff, and verification evidence.
Use for QEMU peripheral, accelerator, MMIO, qdev, or SysBusDevice modeling. Extends qemu-plan and qemu-rlcr-loop; register-bank modeling must use QEMU's registerinfo framework and qtest verification.
Use for adapting a QEMU TCG host backend, including optional op support, constraints, register allocation, host code emission, qemu_ld/st, atomics, and vector ops. Extends qemu-plan and qemu-rlcr-loop.
Use for adding, reviewing, or debugging a guest ISA instruction in a QEMU TCG frontend. Extends qemu-plan and qemu-rlcr-loop; this skill only defines frontend decode/translation decisions.
| name | qemu-build |
| description | Use for configuring, reusing, building, or diagnosing QEMU build directories. Defaults to build and keeps agent-created logs and reports under a .oh-my-qemu task workspace. |
Use this operational skill when the task asks to inspect, configure, build, reconfigure, or diagnose a QEMU build.
This primitive owns only build-directory inspection, configure/build commands, build logs, and build-failure diagnosis. It consumes an artifact root supplied by the caller and does not choose planning, verification, debug, or review workflow steps.
Do not produce source code intended for QEMU upstream submission. Do not add DCO or review trailers.
Default to build/ in the QEMU source tree. Reuse it when suitable.
Before creating or reconfiguring anything, inspect:
build/config.log for the configure command;build/build.ninja for configured state;build/pyvenv/bin/meson for Meson commands;build/meson-logs/meson-log.txt for configure failures;build/meson-info/intro-buildoptions.json for options.Create another directory only when needed to preserve a different configuration, such as sanitizer vs non-sanitizer.
From the QEMU source root:
mkdir -p build
cd build
../configure --target-list=<targets>
Common targets:
x86_64-softmmuaarch64-softmmuriscv64-softmmuloongarch64-softmmux86_64-linux-useraarch64-linux-userUseful options:
--enable-debug--enable-debug-info--enable-trace-backends=log--enable-asan--enable-tsan--enable-ubsanUse ../configure --help for the checked-out QEMU version.
Reconstruct the old command from build/config.log, then change only the needed option.
Preserve:
Do not delete build/ to make an error disappear.
From the source root:
ninja -C build
Prefer narrow targets when possible:
ninja -C build qemu-system-riscv64
ninja -C build tests/qtest/<test-name>
Use verbose mode only for diagnosis:
ninja -C build -v <target>
For generated-source failures, fix the generator input, not generated files in build/.
Write/report:
.oh-my-qemu/<task-slug>/;docs/devel/code-provenance.rst.qemu-build skill.docs/devel/testing/main.rst.