mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-17 00:36:07 +00:00
Fix some usability issues with this command. - add help making it clear that either imgtool must be installed, or the path to imgtool.py must be provided using --tool-path. - in case people don't read that, print a helpful message if imgtool is not installed and --tool-path is not provided. - in case the build directory is not properly set up for an MCUboot chain-loaded image, make the BuildConfiguration inspection more robust, printing out errors using check_force() when values are missing. - mark the --tool option required to print usage and avoid a RuntimeError if it is not provided. - make sure we search for the default build directory before checking for its existence, in case it was not provided Signed-off-by: Marti Bolivar <marti@foundries.io> |
||
---|---|---|
.. | ||
runners | ||
tests | ||
build.py | ||
debug.py | ||
flash.py | ||
README.txt | ||
run_common.py | ||
sign.py | ||
zephyr_ext_common.py |
This directory contains implementations for west commands which are tightly coupled to the zephyr tree. Currently, those are 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 just those files that change along with Zephyr itself. When extending this code, please keep the unit tests (in tests/) up to date. You can run the tests with this command from this directory: $ PYTHONPATH=$(west list --format="{abspath}" west)/src:$PWD py.test Windows users will need to find the path to .west/west/src in their Zephyr installation, then run something like this: > cmd /C "set PYTHONPATH=path\to\.west\west\src:path\to\zephyr\scripts\west_commands && py.test" 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!