MIRRORS/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky.git synced 2025-07-19 12:59:02 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

ref-manual: classes: nativesdk: move note to appropriate section

Browse Source 
The nativesdk- prefix to the recipe filename should only be used when
using the inherit method as the BBCLASSEXTEND method will do some magic
when generating the "implicit" name of the recipe.

This matches the instructions for the native class.

(From yocto-docs rev: 15fe239e1e62b9add737aa732dd7f5e9948ee03d)

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Quentin Schulz 2025-06-06 17:01:48 +02:00 committed by Richard Purdie
parent d349e792c1
commit 474742f808
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
documentation/ref-manual/classes.rst
View File

@ -2082,6 +2082,16 @@ couple different ways:
inherit statement in the recipe after all other inherit statements so
that the :ref:`ref-classes-nativesdk` class is inherited last.
.. note::
When creating a recipe, you must follow this naming convention::
nativesdk-myrecipe.bb
Not doing so can lead to subtle problems because there is code that
depends on the naming convention.
- Or, create a :ref:`ref-classes-nativesdk` variant of any target recipe (e.g.
``myrecipe.bb``) by adding the following to the recipe::
@ -2092,16 +2102,6 @@ couple different ways:
specify any functionality specific to the respective SDK machine or
target case.
.. note::
When creating a recipe, you must follow this naming convention::
nativesdk-myrecipe.bb
Not doing so can lead to subtle problems because there is code that
depends on the naming convention.
Although applied differently, the :ref:`ref-classes-nativesdk` class is used with both
methods. The advantage of the second method is that you do not need to
have two separate recipes (assuming you need both) for the SDK machine