zephyr/scripts/west_commands
Marti Bolivar a1ef6962ae scripts: fix up west build verbosity levels
Adjust them so "west build -v" prints ZEPHYR_BASE and any CMake
commands, but none of the other more esoteric bits of information.

Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
2019-05-06 16:30:05 -04:00
..
runners boards: rv32m1_vega: Use different openocd config file for each core 2019-05-06 14:52:17 -05:00
tests
boards.py scripts: fix and tweak west boards 2019-05-06 16:30:05 -04:00
build_helpers.py west: Renamed cmake.py to zcmake.py 2019-05-04 16:40:06 +02:00
build.py scripts: fix up west build verbosity levels 2019-05-06 16:30:05 -04:00
debug.py
flash.py
README.txt
run_common.py
sign.py
zcmake.py west: build: Construct CalledProcessError with positional args 2019-05-04 20:59:15 +02:00
zephyr_ext_common.py west: Implement CMake helpers in scripts/west_commands 2019-05-03 21:55:13 +02:00

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!