Lines Matching +full:code +full:- +full:format

1 .. _west-zephyr-ext-cmds:
6 This page documents miscellaneous :ref:`west-zephyr-extensions`.
8 .. _west-boards:
20 This command lists all supported boards in a default format. If you prefer to
21 specify the display format yourself you can use the ``--format`` (or ``-f``)
24   west boards -f "{arch}:{name}"
28   west boards -h
30 .. _west-completion:
40 - bash
41 - zsh
42 - fish
48 .. _west-zephyr-export:
50 Installing CMake packages: ``west zephyr-export``
66 .. code-block:: cmake
70 See :zephyr_file:`share/zephyr-package/cmake` for details.
72 .. _west-spdx:
77 This command generates SPDX 2.3 tag-value documents, creating relationships
79 ``SPDX-License-Identifier`` comments in source files are scanned and filled
84 #. Pre-populate a build directory :file:`BUILD_DIR` like this:
86    .. code-block:: bash
88       west spdx --init -d BUILD_DIR
95 #. Build your application using this pre-created build directory, like so:
97    .. code-block:: bash
99       west build -d BUILD_DIR [...]
103    .. code-block:: bash
105       west spdx -d BUILD_DIR
107 This generates the following SPDX bill-of-materials (BOM) documents in
110 - :file:`app.spdx`: BOM for the application source files used for the build
111 - :file:`zephyr.spdx`: BOM for the specific Zephyr source code files used for the build
112 - :file:`build.spdx`: BOM for the built output files
113 - :file:`modules-deps.spdx`: BOM for modules dependencies. Check
114   :ref:`modules <modules-vulnerability-monitoring>` for more details.
116 Each file in the bill-of-materials is scanned, so that its hashes (SHA256 and
118 ``SPDX-License-Identifier`` comment appears in the file.
126 - ``-n PREFIX``: a prefix for the Document Namespaces that will be included in
128   details. If ``-n`` is omitted, a default namespace will be generated
129   according to the default format described in section 2.5 using a random UUID.
131 - ``-s SPDX_DIR``: specifies an alternate directory where the SPDX documents
134 - ``--analyze-includes``: in addition to recording the compiled source code
135   files (e.g. ``.c``, ``.S``) in the bills-of-materials, also attempt to
142 - ``--include-sdk``: with ``--analyze-includes``, also create a fourth SPDX
146    https://spdx.github.io/spdx-spec/v2.2.2/document-creation-information/
148 .. _west-blobs:
154 <bin-blobs>` declared in one or more :ref:`modules <modules>` via their
155 :ref:`module.yml <module-yml>` file.
157 The ``blobs`` command has three sub-commands, used to list, fetch or clean (i.e.
160 You can list binary blobs while specifying the format of the output::
162   west blobs list -f '{module}: {type} {path}'
164 For the full set of variables available in ``-f/--format`` run
165 ``west blobs -h``.
171 Note that, as described in :ref:`the modules section <modules-bin-blobs>`,
180 fetch or clean blobs for by typing the module names as a command-line
183 .. _west-twister:
191   west twister -help
192   west twister -T tests/ztest/base
194 .. _west-bindesc: