zephyr

History

Daniel Leung be8cb89ebd west: esp32: use Python interpreter to execute ESP tool The ESP tool is being executed directly in the esp32 runner, assuming the tool is executable by itself. However, it would fail under Windows as subprocess.check_call() cannot execute Python scripts directly. The fix is to execute the Python interpreter and passing the script path as a command line parameter. Fixes #19098 Signed-off-by: Daniel Leung <daniel.leung@intel.com>		2019-09-25 17:33:28 +02:00
..
completion	west: Add completion command	2019-05-10 13:08:27 +02:00
runners	west: esp32: use Python interpreter to execute ESP tool	2019-09-25 17:33:28 +02:00
tests	scripts: west flash: fix --board-id for pyocd	2019-08-19 11:03:03 +02:00
boards.py	west: boards: Remove accidental comma to fix pylint warning	2019-09-07 08:08:48 -04:00
build_helpers.py	west: flash: Fix exception on build folder guessing	2019-09-07 10:24:17 -04:00
build.py	west: build.py: Remove len() from conditional to fix pylint warning	2019-09-07 08:11:02 -04:00
completion.py	west: completion.py: Fix bad indentation and blank lines at end of file	2019-09-07 08:09:56 -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
README.txt	west: require v0.6.0 or higher	2019-08-05 15:17:45 +02:00
run_common.py	west: runners: Fix typo'd log.wrn() call	2019-09-07 08:05:57 -04:00
sign.py	west: commands: Make functions that don't use 'self' static	2019-09-07 08:04:58 -04:00
zcmake.py	scripts: west_commands: verify minimum cmake version	2019-09-07 10:08:23 -04:00
zephyr_ext_common.py	west: commands: Make functions that don't use 'self' static	2019-09-07 08:04:58 -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=$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!