On Fri, Sep 14, 2018 at 1:20 AM, Dudziak Krzysztof <krzysztof.dudz...@gemalto.com> wrote: > Thanks for feedback from you. > >> If you use BBCLASSEXTEND (ie "the second method") then that recipe naming >> rule doesn't apply. > Looks like section's 6.83 current structure wouldn't reflect this fact well. > Warning is placed directly below > one-sentence and indented text describing to BBCLASSEXTEND-case
Yes, I agree. That part of the documentation could certainly be improved. > krzysiek > > -----Original Message----- > From: Andre McCurdy [mailto:armccu...@gmail.com] > Sent: Friday, 14. September 2018 01:05 > To: Dudziak Krzysztof <krzysztof.dudz...@gemalto.com> > Cc: Burton, Ross <ross.bur...@intel.com>; yocto@yoctoproject.org > Subject: Re: [yocto] inheriting native.bbclass explicitly > > On Thu, Sep 13, 2018 at 6:05 AM, Dudziak Krzysztof > <krzysztof.dudz...@gemalto.com> wrote: >> Current release's reference manual issues in native.bbclass chapter a >> warning: >> "When creating a recipe, you must follow this naming convention: >> native-myrecipe.bb >> Not doing so can lead to subtle problems because code exists that depends on >> the naming convention." > > Looks like a mistake in the documentation. Native only recipes (ie recipes > which use "inherit native" rather than BBCLASSEXTEND) should have "-native" > as a suffix, not "native-" as a prefix. > >> Jethro release manual does not point it out. >> Is this warning really out of relevance for certain past releases e.g. >> Jethro? >> >> Abstracting from question raised above how following two fit all together: >> "When creating a recipe, you must follow this naming convention: >> native-myrecipe.bb" >> and >> " The advantage of the second method is that you do not need to have >> two separate recipes " (2.5.1 Release Reference Manual) > > If you use BBCLASSEXTEND (ie "the second method") then that recipe naming > rule doesn't apply. ie a recipe using BBCLASSEXTEND should not have a > "-native" suffix. > >> krzysiek >> >> -----Original Message----- >> From: Burton, Ross [mailto:ross.bur...@intel.com] >> Sent: Thursday, 13. September 2018 14:00 >> To: Dudziak Krzysztof <krzysztof.dudz...@gemalto.com> >> Cc: yocto@yoctoproject.org >> Subject: Re: [yocto] inheriting native.bbclass explicitly >> >> On 13 September 2018 at 12:39, Dudziak Krzysztof >> <krzysztof.dudz...@gemalto.com> wrote: >>> Thanks for hints. >>> I don't want to have this package on target system. >>> You sound like inheriting explicitly had some major drawback of wide scope. >> >> It won't be included in the image unless you add it to the image. >> >> Ross >> ________________________________ >> This message and any attachments are intended solely for the addressees and >> may contain confidential information. Any unauthorized use or disclosure, >> either whole or partial, is prohibited. >> E-mails are susceptible to alteration. Our company shall not be liable for >> the message if altered, changed or falsified. If you are not the intended >> recipient of this message, please delete it and notify the sender. >> Although all reasonable efforts have been made to keep this transmission >> free from viruses, the sender will not be liable for damages caused by a >> transmitted virus. >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis >> ts.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7CKrzysztof.Du >> dziak%40gemalto.com%7Ced60588df01e4484015c08d619cd5ee6%7C37d0a9db7c464 >> 096bfe31add5b495d6d%7C1%7C0%7C636724767194372674&sdata=8GXUXT5abR3 >> BHWxhzbCf0bbYxYqpU7x6r0ZXbQt7clw%3D&reserved=0 > ________________________________ > This message and any attachments are intended solely for the addressees and > may contain confidential information. Any unauthorized use or disclosure, > either whole or partial, is prohibited. > E-mails are susceptible to alteration. Our company shall not be liable for > the message if altered, changed or falsified. If you are not the intended > recipient of this message, please delete it and notify the sender. > Although all reasonable efforts have been made to keep this transmission free > from viruses, the sender will not be liable for damages caused by a > transmitted virus. -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
