zephyr/scripts/west_commands
Martí Bolívar 34a59168d5 build: clean up west build
The header printed at the beginning of every west build is kind of
annoying. Let's remove it and just print the application source
directory at cmake time instead. The build directory and board are
already printed there, anyway, and that's all IDE users will see.

Let's clean up the BOARD to make it say "board" instead. That matches
the west build --board option name a bit more closely and is still
legible.

Likewise, let's not print any west build messages if we're just
incrementally recompiling. That's noisy.

Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-10 14:53:28 +02:00
..
completion
runners runners: misc-flasher: hotfix 2020-03-04 21:48:09 +02:00
tests board: arc: Switch to generic OpenOCD runner 2020-02-13 10:45:44 +02:00
README.txt
boards.py
build.py build: clean up west build 2020-03-10 14:53:28 +02:00
build_helpers.py scripts: west_commands: fix argument handling with runners.yaml 2020-02-20 09:06:09 +02:00
completion.py
debug.py scripts: west_commands: fix argument handling with runners.yaml 2020-02-20 09:06:09 +02:00
flash.py scripts: west_commands: fix argument handling with runners.yaml 2020-02-20 09:06:09 +02:00
run_common.py scripts: run_common: fix command line --hex-file and friends 2020-02-29 19:38:49 +02:00
sign.py scripts: fix west sign when ZEPHYR_BASE is unset 2020-02-20 09:06:09 +02:00
zcmake.py
zephyr_ext_common.py scripts: fix west sign when ZEPHYR_BASE is unset 2020-02-20 09:06:09 +02: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=$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!