zephyr/doc/guides/west
Martí Bolívar 20ca76fe17 doc: west: troubleshoot no west on PATH on windows
Depending on how people set up their Python, west might not be on
PATH.

I'd like to have a special-purpose step by step guide for how to
handle this in the documentation to save support time when this
happens. I think it's worth special casing since west is the first
runnable program that pip installs onto a new user's system when
they're following the GSG.

Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-08-27 16:06:01 +02:00
..
build-flash-debug.rst doc: west: add pointer to board porting guide for flash/debug 2020-03-25 19:43:30 +01:00
config.rst doc: west: 'west installation' is now 'west workspace' 2020-02-25 23:08:02 +02:00
extensions.rst doc: west: 'west installation' is now 'west workspace' 2020-02-25 23:08:02 +02:00
index.rst doc: west: 0.7.0 documentation 2020-02-07 07:25:41 -06:00
install.rst doc: west: Fix west completion docs 2019-08-12 09:44:37 -07:00
manifest.rst doc: west: 'west installation' is now 'west workspace' 2020-02-25 23:08:02 +02:00
moving-to-west.rst doc: west: 'west installation' is now 'west workspace' 2020-02-25 23:08:02 +02:00
release-notes.rst doc: west: 0.7.0 documentation 2020-02-07 07:25:41 -06:00
repo-tool.rst doc: west: link to modules page instead of source code 2020-04-08 12:00:44 -05:00
sign.rst docs: update west sign docs 2019-06-16 10:16:15 -04:00
troubleshooting.rst doc: west: troubleshoot no west on PATH on windows 2020-08-27 16:06:01 +02:00
west-apis.rst doc: west: 0.7.0 documentation 2020-02-07 07:25:41 -06:00
west-mr-model.png
west-not-found.rst global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
why.rst
without-west.rst doc: west: 'west installation' is now 'west workspace' 2020-02-25 23:08:02 +02:00
zephyr-cmds.rst global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00