Deprecate qemu.cmake in favour of a qemu runner backend · zephyrproject-rtos/zephyr#5501

(9 comments) (0 reactions) (1 assignee)C (15,249 stars) (9,144 forks)batch import

EnhancementGood first issuearea: Build Systemarea: Flashing

説明

Hi,

I suspect we want to eventually rename/alias 'flash' to 'run'. And treat qemu emulation as just another runner backend. I believe this would make it easier for us to maintain the runner and qemu infrastructure, and would make it easier for us to keep the user-interface for flashing and running consistent.

A qemu backend would also allow us to move all the symlink/fifo/pipehandling out of qemu.cmake and into a python runner backend.

It is not clear how difficult it would be to do this.

コントリビューターガイド

技術スタック: cpython
領域: build systemdeveloper experiencetooling
Issue 種別: refactor
難度: 4
推定時間: 3-5 days
活動状況: stale
明確さ: mostly clear
前提条件: CMakePythonZephyr build systemQEMU basics
初心者向け度: 20
調査方針: Examine qemu.cmake in the Zephyr repository to understand current symlink/fifo/pipe handling. Review discussion in issue #5501, particularly comments from maintainers regarding the desired runner backend interface. Investigate existing runner backends in the Python scripts directory to model a new QEMU backend. Propose a plan to move QEMU specific logic out of CMake and into Python, ensuring backward compatibility for the 'flash' command.