[OE-core] how to cleanly centralize a zillion BBCLASSEXTEND += "nativesdk" settings?

Jeremy Puhlman jpuhlman at mvista.com
Tue Mar 3 19:17:40 UTC 2020



On 3/3/2020 6:38 AM, Richard Purdie wrote:
> On Tue, 2020-03-03 at 06:25 -0800, Tim Orling wrote:
>>
>> On Tue, Mar 3, 2020 at 4:32 AM Peter Kjellerstedt <
>> peter.kjellerstedt at axis.com> wrote:
>>>> -----Original Message-----
>>>> From: openembedded-core-bounces at lists.openembedded.org
>>> <openembedded-core-
>>>> bounces at lists.openembedded.org> On Behalf Of
>>> rpjday at crashcourse.ca
>>>> Sent: den 2 mars 2020 13:41
>>>> To: openembedded-core at lists.openembedded.org
>>>> Subject: [OE-core] how to cleanly centralize a zillion
>>> BBCLASSEXTEND +=
>>>> "nativesdk" settings?
>>>>
>>>> layer i'm currently perusing has many, many bbappend files, of
>>> which
>>>> quite a number are nothing more than the single line:
>>>>
>>>>     BBCLASSEXTEND += "nativesdk"
>>>>
>>>> literally, at least a hundred append files are like that. so
>>> rather
>>>> than clutter up the layer with all those trivial .bbappend files,
>>>> can one cram all that into a single .conf file? as i read it, can
>>> i
>>>> do something like:
>>>>
>>>>     BBCLASSEXTEND_append_pn-pkg1 = " nativesdk"
>>>>     BBCLASSEXTEND_append_pn-pkg2 = " nativesdk"
>>>>     ... and on and on ...
>>>>
>>>> and toss all that into a distro.conf file or something?
>>>>
>>>>     and even if that works, is it considered good coding style?
>>>>
>>>> rday
>>> Sounds perfectly fine. We do something similar, but in our case we
>>> need
>>> to add "native" to BBCLASSEXTEND for a whole bunch of recipes.
>>>
>> Should patches be sent to add native and nativesdk? Drop the
>> technical debt by upstreaming...
> I'm torn on this since adding these does have performance impact. We've
> talked about adding them as defaults but it does increase parsing time
> and so on...

Why not a couple of distro level classes?
all-recipes-native
all-recipes-nativesdk

Or something similar.

Then you can turn it on if you need it, and leave it optional to not 
impose a parse performance pentalty on those that don't need or want it.

-- 
Jeremy A. Puhlman
jpuhlman at mvista.com



More information about the Openembedded-core mailing list