From: Dudziak Krzysztof <Krzysztof.Dudziak@gemalto.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: inheriting native.bbclass explicitly
Date: Fri, 14 Sep 2018 08:20:51 +0000 [thread overview]
Message-ID: <VI1PR01MB1070D437258E6D818CC7A980E0190@VI1PR01MB1070.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CAJ86T=UssgCnWjnqzM5PWDumA+4472YZJMTO4dnhQTMvj=r8yA@mail.gmail.com>
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
krzysiek
-----Original Message-----
From: Andre McCurdy [mailto:armccurdy@gmail.com]
Sent: Friday, 14. September 2018 01:05
To: Dudziak Krzysztof <Krzysztof.Dudziak@gemalto.com>
Cc: Burton, Ross <ross.burton@intel.com>; yocto@yoctoproject.org
Subject: Re: [yocto] inheriting native.bbclass explicitly
On Thu, Sep 13, 2018 at 6:05 AM, Dudziak Krzysztof <Krzysztof.Dudziak@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.burton@intel.com]
> Sent: Thursday, 13. September 2018 14:00
> To: Dudziak Krzysztof <Krzysztof.Dudziak@gemalto.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] inheriting native.bbclass explicitly
>
> On 13 September 2018 at 12:39, Dudziak Krzysztof
> <Krzysztof.Dudziak@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.
next prev parent reply other threads:[~2018-09-14 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 9:17 inheriting native.bbclass explicitly Dudziak Krzysztof
2018-09-13 9:24 ` Burton, Ross
[not found] ` <VI1PR01MB1070A7E32F845C1CBA1D57B6E01A0@VI1PR01MB1070.eurprd01.prod.exchangelabs.com>
2018-09-13 9:38 ` Burton, Ross
[not found] ` <VI1PR01MB1070D4F85BC847EF0C3F8651E01A0@VI1PR01MB1070.eurprd01.prod.exchangelabs.com>
2018-09-13 11:23 ` Burton, Ross
2018-09-13 11:39 ` Dudziak Krzysztof
2018-09-13 12:00 ` Burton, Ross
2018-09-13 12:36 ` Dudziak Krzysztof
2018-09-13 13:05 ` Dudziak Krzysztof
2018-09-13 23:05 ` Andre McCurdy
2018-09-14 8:20 ` Dudziak Krzysztof [this message]
2018-09-14 17:23 ` Andre McCurdy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=VI1PR01MB1070D437258E6D818CC7A980E0190@VI1PR01MB1070.eurprd01.prod.exchangelabs.com \
--to=krzysztof.dudziak@gemalto.com \
--cc=armccurdy@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.