Lines Matching refs:import
289 * - ``import``
292 :ref:`west-manifest-import` for details.
417 * - ``import``
420 :ref:`west-manifest-import`.
467 - Support for ``import: path-prefix:`` (:ref:`west-manifest-import-map`)
485 - The ``import:`` feature now supports ``allowlist:`` and
489 compatibility. (:ref:`west-manifest-import`,
490 :ref:`west-manifest-import-map`)
537 :ref:`west-manifest-import` in an inactive project will be ignored by west.
572 :ref:`west-manifest-import` feature.
622 As a restriction, no project may use both ``import:`` and ``groups:``. (This
934 group-filter:`` value behaves when combined with :ref:`west-manifest-import`.
940 are different, and combining ``group-filter`` with ``import`` in west v0.9.x
945 - if you only import one manifest, any groups it disables in its
965 import: true
1008 import: true
1055 import: true
1224 .. _west-manifest-import:
1229 You can use the ``import`` key briefly described above to include projects from
1238 import: ...
1240 import: ...
1242 You can use a "self: import:" to load additional files from the repository
1243 containing your :file:`west.yml`. You can use a "project: ... import:" to load
1257 The ``import`` key can be a boolean, path, mapping, or sequence. We'll describe
1260 - :ref:`Boolean <west-manifest-import-bool>`
1264 - :ref:`Relative path <west-manifest-import-path>`
1268 - :ref:`Mapping with additional configuration <west-manifest-import-map>`
1273 - :ref:`Sequence of paths and mappings <west-manifest-import-seq>`
1287 .. _west-manifest-import-bool:
1292 This is the easiest way to use ``import``.
1294 If ``import`` is ``true`` as a ``projects`` attribute, west imports projects
1296 ``false`` or missing, it has no effect. For example, this manifest would import
1306 import: true # Import west.yml from p1's v1.0 git tag
1308 import: false # Nothing is imported from p2.
1311 It's an error to set ``import`` to either ``true`` or ``false`` inside
1319 import: true # Error
1359 import: true
1398 import: true
1414 be used to import projects from Zephyr. This lets you stay up to date with the
1424 You can only import manifest from the file system if they are in your manifest
1455 import: true # imported projects have lower precedence
1489 - import :file:`zephyr/west.yml` at that ``manifest-rev``
1494 .. _west-manifest-import-path:
1499 The ``import`` value can also be a relative path to a manifest file or a
1501 of the ``projects`` or ``self`` repository the ``import`` key appears in.
1511 import: west.yml
1514 import: p2-manifests
1516 import: submanifests
1518 This will import the following:
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`.
1594 import: true
1596 import: submanifests
1615 :file:`my-repo/west.yml` and :file:`zephyr/west.yml`. In general, an ``import``
1660 .. _west-manifest-import-map:
1665 The ``import`` key can also contain a mapping with the following keys:
1667 - ``file``: Optional. The name of the manifest file or directory to import.
1721 import:
1782 import:
1846 import:
1879 You want to import a manifest and its projects, placing everything into a
1882 For example, suppose you want to import this manifest from project ``foo``,
1917 import:
1939 .. _west-manifest-import-seq:
1944 The ``import`` key can also contain a sequence of files, directories,
1962 import: west.yml
1964 import:
1985 import: true
1987 import: submanifests
1989 import:
2001 ``self: import:`` is always imported first
2004 #. :file:`zephyr/west.yml` is after that, since that's the first ``import`` key
2007 name), since that's the final project ``import``
2014 This section describes how west resolves a manifest file that uses ``import`` a
2020 The ``import`` key can appear in a west manifest's ``projects`` and ``self``
2029 import:
2030 ... # import-1
2032 import:
2033 ... # import-2
2036 import:
2037 ... # import-N
2039 import:
2040 ... # self-import
2042 Import keys are optional. If any of ``import-1, ..., import-N`` are missing,
2043 west will not import additional manifest data from that project. If
2044 ``self-import`` is missing, no additional files in the manifest repository
2060 #. Manifests from ``self-import`` are imported first.
2062 #. Manifests from ``import-1``, ..., ``import-N``, are imported in that order.
2064 When an individual ``import`` key refers to multiple manifest files, they are
2073 This process recurses if necessary. E.g., if ``import-1`` produces a manifest
2074 file that contains an ``import`` key, it is resolved recursively using the same
2086 example, if ``import-1`` contains a project named ``bar``, that is ignored,
2090 The contents of files named by ``import-1`` through ``import-N`` are imported
2134 Manifest files which appear earlier in the import order have higher precedence
2139 - the submanifest resolved from ``self-import`` have group filter ``self-filter``
2141 - the submanifests resolved from ``import-1`` through ``import-N`` have group
2181 current manifest and all its :ref:`imported manifests <west-manifest-import>`:
2188 performing any ``import``\ s.