zephyr/scripts/west_commands
Marti Bolivar ddce583ca2 scripts: west_commands: decouple runners pkg from west
I've had some requests to be able to use code in the runners package
without having west installed.

It turns out to be pretty easy to make this happen, as west is
currently only used for west.log and some trivial helper methods:

- To replace west log, use the standard logging module
- Add an appropriate handler for each runner's logger in
  run_common.py which delegates to west.log, to keep
  output working as expected.

Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
2019-06-26 01:25:54 +02:00
..
completion west: Add completion command 2019-05-10 13:08:27 +02:00
runners scripts: west_commands: decouple runners pkg from west 2019-06-26 01:25:54 +02:00
tests scripts: west_commands: decouple runners pkg from west 2019-06-26 01:25:54 +02:00
boards.py scripts: fix and tweak west boards 2019-05-06 16:30:05 -04:00
build_helpers.py west: build: Configurable build folder format 2019-06-11 00:00:34 +02:00
build.py west: build: Configurable build folder format 2019-06-11 00:00:34 +02:00
completion.py west: Add completion command 2019-05-10 13:08:27 +02: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
README.txt
run_common.py scripts: west_commands: decouple runners pkg from west 2019-06-26 01:25:54 +02:00
sign.py scripts: west sign: test for input file existence 2019-06-16 10:16:15 -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

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!