| Message ID | 20250606-native-options-v1-0-2ad99a184f90@cherry.de |
|---|---|
| Headers | show |
| Series | ref-manual: classes: clarify native/nativesdk classes exclusive options | expand |
On 6 Jun 2025, at 16:01, Quentin Schulz <foss+yocto@0leil.net> wrote: > What happens if I want a recipe to be native and nativesdk but not > target? They can’t if they use BBCLASSEXTEND, as the default is a target. I guess you could do some anonpy and skiprecipe in target builds. Or have explicit native and nativesdk recipes, that share 99% of their content. Ross IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
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? Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> --- 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,