Lines Matching refs:yml
91 # 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:
988 The ``unstable`` group is disabled in :file:`child/west.yml`, and that is not
989 overridden in :file:`parent/west.yml`. Therefore, the final ``group-filter``
998 You are using this :file:`parent/west.yml` manifest:
1002 # parent/west.yml:
1014 And :file:`child/west.yml` contains:
1018 # child/west.yml:
1033 The ``[-unstable]`` group filter in :file:`child/west.yml` is overridden in
1034 :file:`parent/west.yml`, so the ``unstable`` group is enabled. Since
1037 The same :file:`parent/west.yml` file disables the ``optional`` group, so
1040 The final group filter specified by :file:`parent/west.yml` is
1046 You are using this :file:`parent/west.yml` manifest:
1050 # parent/west.yml:
1061 And :file:`child/west.yml` contains:
1065 # child/west.yml:
1086 The ``-unstable`` group filter in :file:`child/west.yml` is overridden in the
1094 The final group filter specified by :file:`parent/west.yml` and the
1230 other manifest files in your :file:`west.yml`. This key can be either a
1243 containing your :file:`west.yml`. You can use a "project: ... import:" to load
1249 #. your :file:`west.yml` file
1253 other files. For example, a project named ``foo`` in your :file:`west.yml`
1295 from the :file:`west.yml` file in that project's root directory. If it's
1297 :file:`west.yml` from the ``p1`` git repository at revision ``v1.0``:
1306 import: true # Import west.yml from p1's v1.0 git tag
1337 │ └── west.yml # the v1.14.1 version of this file is imported
1343 ├── west.yml # main manifest importing zephyr/west.yml v1.14.1
1346 You can do this with the following :file:`my-repo/west.yml`:
1350 # my-repo/west.yml:
1373 repository's :file:`west.yml` at revision ``v1.14.1`` will be cloned into
1389 # my-repo/west.yml:
1413 The contents of :file:`zephyr/west.yml` at the new ``manifest-rev`` will then
1420 :file:`zephyr/west.yml` entirely when resolving imports. West always uses the
1440 # my-repo/west.yml:
1457 # subset of zephyr/west.yml contents at v2.0.0:
1482 :file:`my-repo/west.yml` when defining ``hal_nordic`` there. The value from
1483 :file:`zephyr/west.yml` is ignored entirely. See :ref:`west-manifest-resolve`
1489 - import :file:`zephyr/west.yml` at that ``manifest-rev``
1511 import: west.yml
1520 - the contents of :file:`project-1/west.yml` at ``manifest-rev``, which points
1550 import: west.yml
1552 The setting ``import: west.yml`` means to use the file :file:`west.yml` inside
1556 import is not :file:`west.yml`.
1571 │ ├── 01-libraries.yml
1572 │ ├── 02-vendor-hals.yml
1573 │ └── 03-applications.yml
1574 └── west.yml
1577 manifest file, :file:`my-repo/west.yml`, in addition to projects in
1578 :file:`zephyr/west.yml`. You want to track the latest development code
1585 # my-repo/west.yml:
1600 #. :file:`my-repo/submanifests/01-libraries.yml`
1601 #. :file:`my-repo/submanifests/02-vendor-hals.yml`
1602 #. :file:`my-repo/submanifests/03-applications.yml`
1603 #. :file:`my-repo/west.yml`
1604 #. :file:`zephyr/west.yml`
1608 The :file:`.yml` file names are prefixed with numbers in this example to
1615 :file:`my-repo/west.yml` and :file:`zephyr/west.yml`. In general, an ``import``
1620 precedence. For example, if :file:`01-libraries.yml` defines ``hal_nordic``,
1621 the project by the same name in :file:`zephyr/west.yml` is simply ignored. As
1637 file :file:`00-ci.yml` in :file:`my-repo/submanifests`, with these contents:
1641 # my-repo/submanifests/00-ci.yml:
1652 :file:`my-repo/submanifests`. The projects defined in :file:`00-ci.yml` have
1654 because the name :file:`00-ci.yml` comes before the other file names.
1668 This defaults to :file:`west.yml` if not present.
1698 projects, however. We'll assume the mainline :file:`west.yml` is
1703 # mainline west.yml:
1716 # downstream west.yml:
1764 # mainline west.yml:
1777 # downstream west.yml:
1821 # mainline west.yml:
1841 # downstream west.yml:
1887 # foo/west.yml:
1924 # foo/west.yml:
1957 # my-repo/west.yml:
1962 import: west.yml
1965 - submanifests/01-libraries.yml
1966 - submanifests/02-vendor-hals.yml
1967 - submanifests/03-applications.yml
1978 # my-repo/west.yml
1990 - submanifests/libraries.yml
1991 - submanifests/vendor-hals.yml
1992 - submanifests/applications.yml
1999 they occur (e.g. :file:`libraries.yml` comes before
2000 :file:`applications.yml`, since this is a sequence of files), since the
2002 #. :file:`my-repo/west.yml` is next (with projects ``my-library`` etc. as long
2004 #. :file:`zephyr/west.yml` is after that, since that's the first ``import`` key
2005 in the ``projects`` list in :file:`my-repo/west.yml`
2087 because the top-level :file:`west.yml` has already defined a project by that
2100 ``manifest-rev`` in the ``baz`` project if :file:`baz/west.yml` defines ``P``,
2103 from :file:`baz/west.yml`, which "should" cause ``west update P`` to fail with an
2246 The output is something like ``/path/to/workspace/west.yml``. The path format