Bug 12924 - native.bbclass section
Summary: native.bbclass section
Status: RESOLVED FIXED
Alias: None
Product: Reference
Classification: Documentation
Component: handbook (show other bugs)
Version: 2.5.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.7
Assignee: Randy MacLeod
QA Contact:
URL:
Whiteboard: 14 November 2018: RESOLVED
Depends on:
Blocks:
 
Reported: 2018-09-14 13:05 UTC by krzysztof.dudziak
Modified: 2018-11-14 16:44 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description krzysztof.dudziak 2018-09-14 13:05:06 UTC 
Yocto Release 2.5.1 Project Reference Manual
Section 6.83: native.bbclass
Indicated as to be buggy in: https://lists.yoctoproject.org/pipermail/yocto/2018-September/042543.html

1.
Warning placed in frame specifies the recipe file name scheme to: native-myrecipe.bb.

myrecipe-native.bb should be instead.

2.
If you use BBCLASSEXTEND (ie "the second method") then that recipe naming rule doesn't apply (Andre McCurdy, yocto project discussions ML)
Problem:
Looks like section's current structure wouldn't reflect this fact well. Warning is placed directly below one-sentence and indented text describing the BBCLASSEXTEND-case
Comment 1 Scott Rifenbark 2018-09-26 20:28:45 UTC 
See https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#ref-classes-native for the updates.

thanks,
Scott
Comment 2 Stephen K Jolley 2018-11-08 16:15:42 UTC 
Krzysztof,  can you answer Scott's question about if this corrects the problem?
Comment 3 krzysztof.dudziak 2018-11-08 16:30:03 UTC 
Sorry for delay as I am not familiarized with the process here. As for me chapter 6.83 looks fine now. Does this form of feedback suffice or any field in ticket to be changed by myself? I push also Status to Accepted, please fix if wrong action.
Comment 4 Randy MacLeod 2018-11-08 17:18:58 UTC 
Resolved as per Krzysztof's comment.
Comment 5 Scott Rifenbark 2018-11-14 16:44:29 UTC 
Krzysztof, 

Thanks... I set the doc flag to "done".  The status has already been marked RESOLVED.  So all is good.

Thanks,
Scott