mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
dev-manual/layers.rst: yocto-check-layer: mention --machines and --dependency
The yocto-check-layer script should be run with the --machines arguments to test the different machines present in a BSP layer. Mention it in the documentation. The --dependency can also be used so also mention that. [YOCTO #15974] Cc: Mark Hatle <mark.hatle@kernel.crashing.org> (From yocto-docs rev: 2cd7b5c83978819179b8a47e213b9812b97d5720) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
c034e6de68
commit
d9bd693589
@@ -376,6 +376,21 @@ directory::
|
|||||||
Be sure to provide the actual directory for your
|
Be sure to provide the actual directory for your
|
||||||
layer as part of the command.
|
layer as part of the command.
|
||||||
|
|
||||||
|
You should pass the dependencies of your layer using the ``--dependency``
|
||||||
|
argument::
|
||||||
|
|
||||||
|
$ source oe-init-build-env
|
||||||
|
$ yocto-check-layer --dependency <layer1_directory> <layer2_directory> ... -- your_layer_directory
|
||||||
|
|
||||||
|
For :term:`BSP <Board Support Package (BSP)>` layers, the ``--machines``
|
||||||
|
argument should be passed as part of the command::
|
||||||
|
|
||||||
|
$ source oe-init-build-env
|
||||||
|
$ yocto-check-layer --machines <machine1> <machine2> ... -- your_layer_directory
|
||||||
|
|
||||||
|
These machines are the ones present in your BSP layer, in the ``conf/machine/``
|
||||||
|
directory.
|
||||||
|
|
||||||
Entering the command causes the script to determine the type of layer
|
Entering the command causes the script to determine the type of layer
|
||||||
and then to execute a set of specific tests against the layer. The
|
and then to execute a set of specific tests against the layer. The
|
||||||
following list overviews the test:
|
following list overviews the test:
|
||||||
|
|||||||
Reference in New Issue
Block a user