Lines Matching +full:repo +full:- +full:path
1 .. _beyond-gsg:
6 The :ref:`getting_started` gives a straight-forward path to set up
11 .. _python-pip:
22 ``--user`` flag to the ``pip3`` command when installing new packages. This is
25 information about pip\ [#pip]_, including `information on -\\-user`_.
27 - On Linux, make sure ``~/.local/bin`` is at the front of your :envvar:`PATH`
28 :ref:`environment variable <env_vars>`, or programs installed with ``--user``
29 won't be found. Installing with ``--user`` avoids conflicts between pip
30 and the system package manager, and is the default on Debian-based
33 - On macOS, `Homebrew disables -\\-user`_.
35 - On Windows, see the `Installing Packages`_ information on ``--user`` if you
38 On all operating systems, pip's ``-U`` flag installs or updates the package if the
63 a cross-compiler and related tools which are different from the compiler
70 :ref:`board-level documentation <boards>`).
103 The Zephyr project source is maintained in the `GitHub zephyr repo
104 <https://github.com/zephyrproject-rtos/zephyr>`_. External modules used
106 <https://github.com/zephyrproject-rtos/>`_. Because of these
107 dependencies, it's convenient to use the Zephyr-created :ref:`west
109 code. See :ref:`west-basics` for more details.
114 name that does not contain a space anywhere in the path.
116 .. code-block:: console
124 repo.
140 .. code-block:: console
142 # replace zephyrproject with the path you gave west init
153 .. _gs-board-aliases:
162 .. code-block:: cmake
173 ``cmake -DBOARD=pca10028`` and ``west -b pca10028``.
188 Let's build the :zephyr:code-sample:`blinky` sample application.
199 .. code-block:: console
205 .. zephyr-app-commands::
216 documented in :ref:`samples-and-demos`.
220 add the parameter ``-p=auto`` to ``west build`` to clean out settings
227 ``west flash``. This may require board-specific tool installation and
233 .. _setting-udev-rules:
246 permission by non-root users to certain USB-connected devices.
248 The OpenOCD (On-Chip Debugger) project conveniently provides a rules
249 file that defined board-specific rules for most Zephyr-supported
250 arm-based boards, so we recommend installing this rules
251 file by downloading it from their sourceforge repo, or if you've
258 …wget -O 60-openocd.rules https://sf.net/p/openocd/code/ci/master/tree/contrib/60-openocd.rules?for…
259 sudo cp 60-openocd.rules /etc/udev/rules.d
263 …sudo cp ${ZEPHYR_SDK_INSTALL_DIR}/sysroots/x86_64-pokysdk-linux/usr/share/openocd/contrib/60-openo…
267 sudo udevadm control --reload
271 board-specific documentation (:ref:`boards`) for further information if
279 the x86 or ARM Cortex-M3 architectures. (QEMU is included with the Zephyr
284 add path to QEMU installation folder to PATH environment variable.
287 ``QEMU_BIN_PATH`` to the path of QEMU installation folder.
292 .. zephyr-app-commands::
293 :zephyr-app: samples/hello_world
294 :host-os: unix
298 To exit QEMU, type :kbd:`Ctrl-a`, then :kbd:`x`.
300 Use ``qemu_cortex_m3`` to target an emulated Arm Cortex-M3 sample.
308 on Linux. See :ref:`native_sim` for more information. On 64-bit host operating systems, you
309 need to install a 32-bit C library, or build targeting :ref:`native_sim/native/64<native_sim32_64>`.
313 .. zephyr-app-commands::
314 :zephyr-app: samples/hello_world
315 :host-os: unix
321 .. code-block:: console
323 west build -t run
327 Press :kbd:`Ctrl-C` to exit.
329 You can run ``./build/zephyr/zephyr.exe --help`` to get a list of available
355 running different Zephyr-based binaries on CPU cores of differing
360 .. _information on -\\-user:
361 https://packaging.python.org/tutorials/installing-packages/#installing-to-the-user-site
362 .. _Homebrew disables -\\-user:
363 https://docs.brew.sh/Homebrew-and-Python#note-on-pip-install---user
365 https://packaging.python.org/tutorials/installing-packages/