mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-03 07:54:35 +00:00
Rolling yet another parser turns out to be the best way to let west extensions respond to Kconfig values. See source code comments in the patch for details. The sanitylib library has some similar functionality but it isn't exactly the same, and it gets strings wrong. For example, that parser can't handle this option: CONFIG_FOO="he said \"no\" to me" This one can, and it has a couple of other features we'll find useful for west extensions eventually besides. (Not to mention that sanitylib also rolled its own CMake cache parser, which also exists in west_commands.) 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 | ||
README.txt | ||
run_common.py | ||
sign.py | ||
zcmake.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=$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\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!