mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-03 11:04:17 +00:00
I keep seeing people miss the --context option in the "west flash --help" output. This option is very important for understanding the runner-specific options and state, and missing it means people get confused about what west flash, debug, etc. can do and are doing. Try to avoid this problem by adding a big fat banner about the omission of runner-specific options in the main help output, and provide more hints about how to use --context. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> |
||
---|---|---|
.. | ||
completion | ||
runners | ||
tests | ||
boards.py | ||
build_helpers.py | ||
build.py | ||
completion.py | ||
debug.py | ||
export.py | ||
flash.py | ||
mypy.ini | ||
README.txt | ||
run_common.py | ||
run_tests.py | ||
sign.py | ||
zcmake.py | ||
zephyr_ext_common.py |
This directory contains implementations for west commands which are tightly coupled to the zephyr tree. This includes the build, flash, and debug commands. Before adding more here, consider whether you might want to put new extensions in upstream west. For example, any commands which operate on the multi-repo need to be in upstream west, not here. Try to limit what goes in here to Zephyr-specific features. When extending this code, please keep the unit tests (in tests/) up to date. The mypy static type checker is also run on the runners package. To run these tests locally on Windows, run: py -3 run_tests.py On macOS and Linux: ./run_tests.py Note that these tests are run as part of Zephyr's CI when submitting an upstream pull request, and pull requests which break the tests cannot be merged. Thanks!