Lines Matching full:you
36 If you're behind a corporate firewall and may have proxy or other issues,
40 If you can get the ``git fetch`` command to run successfully without prompting
41 for a password when you run it directly, you will be able to run ``west
51 First, make sure you've installed west; see :ref:`west-install`. Then try
55 You need to find the directory containing :file:`west.exe`, then add it to your
56 :envvar:`PATH`. (This :envvar:`PATH` change should have been done for you when
57 you installed Python and pip, so ordinarily you should not need to follow these
76 #. If you see ``west.exe`` in the ``scripts`` directory, add the full path to
83 #. Close your ``cmd.exe`` window and open a new one. You should be able to run
121 packages, so you may need to do some additional work to get it installed on
130 If you see an unexpected error like this when trying to run a Zephyr extension
142 The most likely cause is that you're running the command outside of a
146 To fix this, you have two choices:
149 directory you created when you :ref:`got started <getting_started>`).
158 If you're unsure whether a command is built-in or an extension, run ``west
182 If you see this error when running ``west init``:
190 Then you have an old version of west installed, and are trying to use it in a
198 #. Back up any contents of :file:`zephyrproject/.west/config` that you want to
199 save. (If you don't have any configuration options set, it's safe to skip
202 #. Completely remove the :file:`zephyrproject/.west` directory (if you don't,
203 you will get the "already in a workspace" error message discussed next).
210 You may see this error when running ``west init`` with west 0.6:
216 If this is unexpected and you're really trying to create a new west workspace,
220 This is intentional; it allows you to put your Zephyr applications in