inheriting native.bbclass explicitly

inheriting native.bbclass explicitly

[Dudziak Krzysztof]

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Hi,

YP reference manual chapter 6.83 "native.bbclass"
https://www.yoctoproject.org/docs/2.5.1/ref-manual/ref-manual.html#ref-classes-native reads:
"*Create a myrecipe-native.bb that inherits the native class.
If you use this method, you must order the inherit statement in the recipe
after all other inherit statements so that the native class is inherited last."

Is this rule's scope literally each single recipe separately
or rather the compound .bb file + set of matching .bbappends?

I am going to use that method for building autoconf-archive package
as for device built here this package is needed only on build system and in no case on target system.

Regards
krzysiek
________________________________
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.

[-- Attachment #2: Type: text/html, Size: 3752 bytes --]

Re: inheriting native.bbclass explicitly

[Burton, Ross]

On 13 September 2018 at 10:17, Dudziak Krzysztof
<Krzysztof.Dudziak@gemalto.com> wrote:
> Is this rule’s scope literally each single recipe separately
>
> or rather the compound .bb file + set of matching .bbappends?

Compound.

> I am going to use that method for building autoconf-archive package
>
> as for device built here this package is needed only on build system and in
> no case on target system.

No need, the recipe already has BBCLASSEXTEND=native so you can just
depend on autoconf-archive-native.

Ross

Re: inheriting native.bbclass explicitly

[Burton, Ross]

Adding yocto@ back to CC.  Please remember to mail the list and not the sender.

On 13 September 2018 at 10:34, Dudziak Krzysztof
<Krzysztof.Dudziak@gemalto.com> wrote:
> Will BBCLASSEXTEND=native fashion also build target system package?
> This is what is not needed (autoconf-archive on target system).
> Therefore thoughts turn to another approach.

BBCLASSEXTEND works by taking a target recipe and dynamically creating
another version of it.

So autoconf-archive.bb is written as a target recipe but because it
contains BBCLASSEXTEND="native nativesdk", there also exists
autoconf-archive-native and nativesdk-autoconf-archive.

Ross

Re: inheriting native.bbclass explicitly

[Burton, Ross]

CCing the list again.  Please remember to reply to the list.

On 13 September 2018 at 11:42, Dudziak Krzysztof
<Krzysztof.Dudziak@gemalto.com> wrote:
> Is it possible for one Bitbake target to check list and order of classes inherited?

bitbake -e [recipe] will show you what was parsed.

In this situation I wouldn't worry too much.  It's best to use
BBCLASSEXTEND instead of inherit native directly anyway.

Ross

Re: inheriting native.bbclass explicitly

[Dudziak Krzysztof]

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.

I am familiarized with bitbake -e ....
I know it as a way to print package/image tasks variables.
But how its output shows the list of classes inherited and the order they are inherited by Bitbake target?
Is any variable indicating this included in its output?

krzysiek

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Thursday, 13. September 2018 13:23
To: Dudziak Krzysztof <Krzysztof.Dudziak@gemalto.com>; Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: [yocto] inheriting native.bbclass explicitly

CCing the list again.  Please remember to reply to the list.

On 13 September 2018 at 11:42, Dudziak Krzysztof <Krzysztof.Dudziak@gemalto.com> wrote:
> Is it possible for one Bitbake target to check list and order of classes inherited?

bitbake -e [recipe] will show you what was parsed.

In this situation I wouldn't worry too much.  It's best to use BBCLASSEXTEND instead of inherit native directly anyway.

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.

Re: inheriting native.bbclass explicitly

[Burton, Ross]

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

Re: inheriting native.bbclass explicitly

[Dudziak Krzysztof]

Got it and will follow your recommendation. Thanks.

-----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.

Re: inheriting native.bbclass explicitly

[Dudziak Krzysztof]

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."

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)

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.

Re: inheriting native.bbclass explicitly

[Andre McCurdy]

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://lists.yoctoproject.org/listinfo/yocto

Re: inheriting native.bbclass explicitly

[Dudziak Krzysztof]

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&amp;data=02%7C01%7CKrzysztof.Du
> dziak%40gemalto.com%7Ced60588df01e4484015c08d619cd5ee6%7C37d0a9db7c464
> 096bfe31add5b495d6d%7C1%7C0%7C636724767194372674&amp;sdata=8GXUXT5abR3
> BHWxhzbCf0bbYxYqpU7x6r0ZXbQt7clw%3D&amp;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.

Re: inheriting native.bbclass explicitly

[Andre McCurdy]

On Fri, Sep 14, 2018 at 1:20 AM, Dudziak Krzysztof
<Krzysztof.Dudziak@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: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&amp;data=02%7C01%7CKrzysztof.Du
>> dziak%40gemalto.com%7Ced60588df01e4484015c08d619cd5ee6%7C37d0a9db7c464
>> 096bfe31add5b495d6d%7C1%7C0%7C636724767194372674&amp;sdata=8GXUXT5abR3
>> BHWxhzbCf0bbYxYqpU7x6r0ZXbQt7clw%3D&amp;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.