zephyr/scripts/west_commands
David B. Kinder 6000a6205a doc: prepare for improving doc API linking
Linking to API material requires knowing the pecularities of how
doxygen, sphinx, and breathe work. In an attempt to hide some of this
we're preparing the current docs to allow use of configuration defaults
that will let us more simply use a default role that will hunt for a
reference target in the various domains that are available by using a
default "role" of "all".  This will let us use the simple notation
`functionname` or `typename` without fully specifying the reference as
:c:func:`functionname`.

This patch cleans up exising docs that were (incorrectly) using single
backtics where double backtics should have been used, and also found
some typos (such as a space between the role name and the reference,
such as :file: `filename`, and a missing colon such as
c:func:`functionname`)

This is a start to address issue #14313

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2019-03-15 05:47:19 +01:00
..
runners doc: prepare for improving doc API linking 2019-03-15 05:47:19 +01:00
tests west_commands: pyocd: Sector erase by default 2019-03-12 16:52:14 +01:00
build.py west: commands: build: Specify source dir without a flag 2019-03-08 21:19:42 +01: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_commands: add information on running tests 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: sign.py: usability fixes 2019-02-15 21:07:10 +01:00
zephyr_ext_common.py scripts: west_commands: refactor run_common.py 2019-02-07 08:44:19 -05: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!