ref-manual: classes: clarify native/nativesdk classes exclusive options
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected] change-id 20250606-native-options-9456be705f04Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | ref-manual: classes: reword to clarify that native/nativesdk options are exclusivedocumentation/ | +4 | 0 replies | |
| 2/2 | ref-manual: classes: nativesdk: move note to appropriate sectiondocumentation/ | +10 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] ref-manual: classes: clarify native/nativesdk classes exclusive options
Someone recently misread the documentation and did both options, that is name the recipe with -native and add BBCLASSEXTEND = "native" to it.
So this hopefully make it clearer by rewording the second item in the bullet list.
At the same time, put the nativesdk note about the filename for the first bullet point within the first bullet point, like for the similar native note.
Reading through this class documentation for the first time, I had this random thought:
What happens if I want a recipe to be native and nativesdk but not target?
---
Quentin Schulz (2):
ref-manual: classes: reword to clarify that native/nativesdk options are exclusive
ref-manual: classes: nativesdk: move note to appropriate section
documentation/ref-manual/classes.rst | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-)
---
base-commit: 406e8a8e30404c0538f5aa46f211540bae2b206b
change-id: 20250606-native-options-9456be705f04
Best regards,
Signature · 1 line
Quentin Schulz <[email protected]>