Home
last modified time | relevance | path

Searched refs:yml (Results 1 – 25 of 49) sorted by relevance

12

/Zephyr-latest/scripts/ci/
Dtwister_ignore.txt11 .codecov.yml
17 .github/workflows/issue_count.yml
18 .github/workflows/stats_merged_prs.yml
19 .github/workflows/assigner.yml
20 .github/workflows/daily_test_version.yml
21 .github/workflows/do_not_merge.yml
22 .github/workflows/stale_issue.yml
23 .github/workflows/stale-workflow-queue-cleanup.yml
24 .github/workflows/greet_first_time_contributor.yml
26 .github/workflows/backport_issue_check.yml
[all …]
/Zephyr-latest/scripts/west_commands/
Dpatch.py316 yml = yaml.load(f, Loader=SafeLoader)
317 return pykwalify.core.Core(source_data=yml, schema_data=patches_schema).validate()
328 yml = self.load_yml(args, args.subcommand in ["gh-fetch"])
329 if yml is None:
342 method[args.subcommand](args, yml, args.dst_modules)
344 def apply(self, args, yml, dst_mods=None): argument
345 patches = yml.get("patches", [])
415 self.clean(args, yml, patched_mods)
419 def clean(self, args, yml, dst_mods=None): argument
420 clean_cmd = yml["clean-command"]
[all …]
/Zephyr-latest/doc/build/snippets/
Dwriting.rst10 Snippets are defined using YAML files named :file:`snippet.yml`.
12 A :file:`snippet.yml` file contains the name of the snippet, along with
79 :file:`snippet.yml` files underneath a subdirectory named :file:`snippets/`,
83 system will look for :file:`snippet.yml` files underneath the following
89 The :file:`snippet.yml` files can be nested anywhere underneath these
92 #. In any :ref:`module <modules>` whose :file:`module.yml` file provides a
96 :file:`module.yml` file:
103 And then any :file:`snippet.yml` files in ``baz/snippets`` will
141 This :file:`snippet.yml` adds :file:`foo.overlay` to the build:
150 :file:`snippet.yml`.
[all …]
/Zephyr-latest/doc/develop/west/
Dmanifest.rst91 # i.e. the repository containing west.yml
286 file is named :file:`west-commands.yml` by convention. See
378 :file:`west.yml`:
386 west-commands: scripts/west-commands.yml
392 the location of the corresponding :file:`west-commands.yml` relative to the
445 The pykwalify schema :file:`manifest-schema.yml` in the `west source code
956 You are using this :file:`parent/west.yml` manifest:
960 # parent/west.yml:
971 And :file:`child/west.yml` contains:
975 # child/west.yml:
[all …]
Dextensions.rst30 See :file:`zephyr/scripts/west-commands.yml` and the
60 #. Add information about it to a :file:`west-commands.yml` file.
61 #. Make sure the :file:`west-commands.yml` file is referenced in the
135 Step 2: Add or Update Your :file:`west-commands.yml`
138 You now need to add a :file:`west-commands.yml` file to your project which
172 :file:`west-commands.yml` file to get the basic information it needs to display
176 multiple files, your :file:`west-commands.yml` will look something like this:
203 See the file :file:`west-commands-schema.yml` in the `west repository`_ for a
204 schema describing the contents of a :file:`west-commands.yml`.
209 Finally, you need to specify the location of the :file:`west-commands.yml` you
[all …]
Dworkspaces.rst164 its :ref:`modules` in its :file:`west.yml`
178 and names other projects required to build it in its :file:`west.yml`. This
194 │   └── west.yml # main manifest with optional import(s) and override(s)
201 └── west.yml # This can be partially imported with lower precedence or ignored.
205 Here is an example :file:`application/west.yml` which uses
211 # Example T2 west.yml, using manifest imports.
227 Another way to do the same thing is to copy/paste :file:`zephyr/west.yml`
228 to :file:`application/west.yml`, adding an entry for the zephyr
243 west-commands: scripts/west-commands.yml
258 :file:`zephyr/west.yml` revision, instead of having to be copy/pasted (and
[all …]
Dbasics.rst32 │ ├── west.yml # manifest file
85 file is named :file:`west.yml` by default; this can be overridden using the
150 #. Set ``manifest.file`` to ``west.yml``
176 (e.g. ``zephyr``) and ``manifest.file`` (e.g. ``west.yml``) options.
178 :file:`zephyrproject/zephyr/west.yml`).
Dbuilt-in.rst56 The ``--mf`` option defaults to ``west.yml``. Since west v0.10.1, west will use
72 As above, ``--mf`` defaults to ``west.yml``.
94 :file:`west.yml`, and updates each project specified there.
/Zephyr-latest/doc/build/flashing/
Dconfiguration.rst20 * ``soc.yml`` (in soc folder)
21 * ``board.yml`` (in board folder)
26 Configuration is applied in the yml file by using a ``runners`` map with a single ``run_once``
33 target sets. Board targets are regular expression matches, for ``soc.yml`` files each set of
35 qualifiers are allowed, board names must be omitted from these entries). For ``board.yml``
41 An example flashing configuration for a ``soc.yml`` is shown below in which the ``--recover``
/Zephyr-latest/submanifests/
DREADME.txt2 in this directory will be included in the main west.yml file sorted by
Dexample.yaml.sample1 # Example manifest file you can include into the main west.yml file.
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_backporting.rst6 …zephyr repository itself and the MCUmgr :ref:`module <modules>` defined in :zephyr_file:`west.yml`.
86 #. Update ``west.yml`` within Zephyr, creating a pull-request to update the MCUmgr library referenc…
97 #. Update ``west.yml`` within Zephyr, creating a pull-request to update the MCUmgr library referenc…
113 #. Ensure that the author of the fix has also provided the ``west.yml`` update for Zephyr 2.7.
156 Merge west.yml
159 As an MCUmgr maintainer, you may not be able to merge the ``west.yml`` update, to introduce the fix…
Dmcumgr_handlers.rst163 without needing to duplicate the code in each application's source tree, see :ref:`module-yml` for
166 Example zephyr/module.yml
170 module directory, and would be placed at ``zephyr/module.yml``:
/Zephyr-latest/
D.editorconfig50 [*.{yml,yaml}]
/Zephyr-latest/doc/develop/
Dmodules.rst53 Modules are repositories that contain a :file:`zephyr/module.yml` file, so that
56 section in the :file:`west.yml` manifest file.
73 * The module repository codebase shall include a *module.yml* file in a
87 * Module repositories names should be explicitly set in the :file:`zephyr/module.yml` file.
332 * document (for example in the module README or .yml file) the default license
449 .. _module-yml:
454 A module can be described using a file named :file:`zephyr/module.yml`.
455 The format of :file:`zephyr/module.yml` is described in the following:
463 The name should be specified in the :file:`zephyr/module.yml` file. This will
494 :file:`zephyr/module.yml`.
[all …]
/Zephyr-latest/cmake/modules/
Dzephyr_module.cmake13 # The `<module>/zephyr/module.yml` file specifies whether the build files are
19 # It looks for: <module>/zephyr/module.yml or
23 # search for zephyr/module.yml from the current workspace's manifest.
25 # If the module.yml file specifies that build files are located in a
Dsoc.cmake35 set_property(DIRECTORY APPEND PROPERTY CMAKE_CONFIGURE_DEPENDS ${dir}/soc.yml)
Dboards.cmake144 if(HWMv2 AND NOT EXISTS ${BOARD_DIR}/board.yml)
207 set_property(DIRECTORY APPEND PROPERTY CMAKE_CONFIGURE_DEPENDS ${dir}/board.yml)
259 "revision.cmake is not used, revisions must be defined in '${BOARD_DIR}/board.yml'"
/Zephyr-latest/doc/hardware/porting/
Dsoc_porting.rst64 ├── soc.yml
76 #. :file:`soc.yml`: a YAML file describing the high-level meta data of the
91 If the ``soc.yml`` describes a SoC family and series, then those must also
126 :file:`soc.yml` file as:
249 :file:`soc.yml` file.
Dboard_porting.rst260 ├── board.yml
276 #. :file:`board.yml`: a YAML file describing the high-level meta data of the
351 :file:`board.yml` must describe those in a list as:
763 :file:`board.yml`.
811 revision section in :file:`board.yml`.
879 field in the ``revision`` section of the :file:`board.yml` must be written as:
937 To extend an existing board, first create a :file:`board.yml` in your extended
956 ├── board.yml
1020 ``west.yml`` manifest file. Any board changes are required to be submitted to
/Zephyr-latest/doc/contribute/
Dexternal.rst109 Integrating external code into the main :file:`west.yml` manifest file is
126 default. (:file:`submanifests/optional.yml`).
154 This may require adding an entry in the :file:`MAINTAINERS.yml` as part of the
227 project in the main :file:`west.yml` manifest. Therefore, this section does not
247 :file:`west.yml` manifest. More info on optional projects can be found in
266 https://github.com/zephyrproject-rtos/zephyr/blob/main/west.yml
Dbin_blobs.rst48 The blobs themselves must be specified in the :ref:`module.yml
56 corresponding :file:`module.yml` file. A specification for a blob must contain:
214 removed from :file:`zephyr/west.yml` at any time due to lack of responsiveness or
/Zephyr-latest/doc/develop/manifest/
Dindex.rst54 Zephyr's :file:`west.yml`.
/Zephyr-latest/doc/develop/sca/
Dindex.rst51 ``-DSCA_ROOT=<sca_root>``, or added by a Zephyr module in its :file:`module.yml`
/Zephyr-latest/cmake/
Dllext-edk.cmake14 # The script expects a build_info.yml file in the project binary directory.
155 set(build_info_file ${PROJECT_BINARY_DIR}/../build_info.yml)

12