ref-manual: classes: reword to clarify that native/nativesdk options are exclusive

We explain how to create a native (nativesdk) recipe in two different
ways via a bullet list but reading quickly the instructions may mislead
one into doing both options whereas they are incompatible.

This rewords both the nativesdk and native sections so that the second
bullet point starts with an Or and explicit that this applies to target
recipes.

(From yocto-docs rev: 6d0d338a5f2686ddeee5eed7b6e05f3db800d33a)

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:47 +02:00 committed by Richard Purdie
parent ea635ace50
commit d349e792c1

View File

@ -2050,7 +2050,8 @@ a couple different ways:
Not using this naming convention can lead to subtle problems
caused by existing code that depends on that naming convention.
- Create or modify a target recipe that contains the following::
- Or, create a :ref:`ref-classes-native` variant of any target recipe (e.g.
``myrecipe.bb``) by adding the following to the recipe::
BBCLASSEXTEND = "native"
@ -2081,7 +2082,8 @@ couple different ways:
inherit statement in the recipe after all other inherit statements so
that the :ref:`ref-classes-nativesdk` class is inherited last.
- Create a :ref:`ref-classes-nativesdk` variant of any recipe by adding the following::
- Or, create a :ref:`ref-classes-nativesdk` variant of any target recipe (e.g.
``myrecipe.bb``) by adding the following to the recipe::
BBCLASSEXTEND = "nativesdk"