[OE-core] [PATCH 0/2] package.bbclass: improve auto debug package splitting order

Hongxu Jia hongxu.jia at windriver.com
Mon Sep 17 12:18:13 UTC 2018


On 2018年09月17日 20:06, richard.purdie at linuxfoundation.org wrote:
> On Fri, 2018-09-14 at 16:49 +0800, Hongxu Jia wrote:
>> Hi RP,
>>
>> Is it necessary to split multiple sub dbg packages or only
>> one dbg is allowed? If the former, this fix makes sense.
> Only one is recommended and the code only works properly in some cases
> for one. I'd like to be in a position where we could have that as the
> only thing we supported but its simply not practical in some cases.
>
> The debug package dependency handling probably needs a rethink but that
> would be 2.7 development cycle, its too late for 2.6 now.
>
>> I know in oe-core, almost one dbg package per recipe, but
>> in oe, 21 recipes have extra sub dbg package and 18 of them
>> did not set NOAUTOPACKAGEDEBUG = "1".
>>
>> So rather than modify them one by one tediously, how about to
>> improve auto debug package splitting order? If ${PN}-dbg exists,
>> split the unsplit debug file to ${PN}-dbg, if ${PN}-dbg does not
>> exist, still split them to first dbg package.
> I don't really want to encourage multiple -dbg packages per recipe and
> I am a little concerned about making changes to the core packaging code
> with the release coming up. Fixing the recipes, although tedious may be
> safer/better rather than encouraging people to do things which aren't
> well supported.

Got it, I will fix affected recipes

Thanks for replying

//Hongxu

> Cheers,
>
> Richard





More information about the Openembedded-core mailing list