zephyr

History

Marti Bolivar 0396b6e64c scripts: west build: propagate verbosity to cmake generator When run as "west -v build", make sure that the underlying build tool is run in verbose mode as well (if the generator is known to support it, which is the case for Unix Makefiles and Ninja based generators). The per-generator hacks here are needed to support CMake 3.13. If we move to CMake 3.14 or later, we can just run "cmake --build BUILD -v" and be done with it. Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>		2019-05-07 15:49:16 +02:00
..
runners	boards: rv32m1_vega: Use different openocd config file for each core	2019-05-06 14:52:17 -05:00
tests	scripts: Remove unused imports in all Python scripts	2019-03-28 11:06:20 -05:00
README.txt	west_commands: add information on running tests	2019-01-29 10:15:01 +01:00
boards.py	scripts: fix and tweak west boards	2019-05-06 16:30:05 -04:00
build.py	scripts: west build: propagate verbosity to cmake generator	2019-05-07 15:49:16 +02:00
build_helpers.py	scripts: make west build -h fit on a screen	2019-05-06 16:30:05 -04:00
debug.py	scripts: west commands: add text for "west --help"	2019-01-29 10:15:01 +01:00
flash.py	scripts: west commands: add text for "west --help"	2019-01-29 10:15:01 +01:00
run_common.py	scripts: west_commands: refactor run_common.py	2019-02-07 08:44:19 -05:00
sign.py	west: fix import error on sign.py	2019-05-07 08:36:29 -04:00
zcmake.py	west: Fix unused import and variable	2019-05-07 08:12:34 -04:00
zephyr_ext_common.py	west: Fix unused import and variable	2019-05-07 08:12:34 -04:00

README.txt

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!