The introduction of sysbuild and west build / flash / debug / etc. support raises questions regarding how to handle user specified runner arguments. Some arguments may be acceptable for all domains, whereas others are only valid for a single or few domains in a multi domain build. Therefore, consider the usages of runner specific options experimental when applied to multiple domains. The following warning is printed to the user when using runner specific arguments on multiple domains: > WARNING: Specifying runner options for multiple domains is > experimental. > If problems are experienced, please specify a single domain using > '--domain <domain>' Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| completion | ||
| fetchers | ||
| runners | ||
| tests | ||
| zspdx | ||
| blobs.py | ||
| boards.py | ||
| build_helpers.py | ||
| build.py | ||
| completion.py | ||
| debug.py | ||
| domains.py | ||
| export.py | ||
| flash.py | ||
| mypy.ini | ||
| README.txt | ||
| run_common.py | ||
| run_tests.py | ||
| sign.py | ||
| spdx.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!