9c92baa73f
Consolidate creation of edtlib.EDT objects from a build directory's devicetree into one place by loading it from build/zephyr/edt.pickle everywhere. A previous commit creates edt.pickle from gen_defines.py. In addition to probably speeding things up slightly by not reparsing the devicetree, the main benefit of this approach is creating a single point of truth for the bindings directories and warnings configuration, meaning we don't have to worry about them getting out of sync while being passed around between devicetree creation and usage time. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> |
||
---|---|---|
.. | ||
completion | ||
runners | ||
tests | ||
boards.py | ||
build.py | ||
build_helpers.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!