[oe] [PATCH 00/19] 19 recipes to split one dpg package only

[Andreas Müller]

On Tue, Sep 18, 2018 at 3:57 AM, Hongxu Jia <hongxu.jia at windriver.com> wrote:
> On 2018年09月18日 09:41, Hongxu Jia wrote:
>>
>> On 2018年09月18日 02:40, Andreas Müller wrote:
>>>
>>> You know that this explodes image size - because dbg package RDEPENDS
>>> on all non debug packages now - or did I miss something.
>>>
>>> E.G fontforge: We need all the python-dbg in the iamge now
>>>
>>> With this images with dbg-packages turn into non usable.
>>>
>>> Haven't got the point what gets better by doing so
>>
>>
> Do you mean previous sub python-dbg only 56K, but after applied this fix,
> the image size enlarged to 24M?
>
> du -sh packages-split/fontforge-dbg/usr/lib/python2.7/site-packages/
> 56K packages-split/fontforge-dbg/usr/lib/python2.7/site-packages/
>
> du -sh packages-split/fontforge-dbg/
> 24M     packages-split/fontforge-dbg/
>
> I doubt that could gdb work correctly that only python-dbg
> without debug library? (Maybe gdb stop at libraries)
>
> packages-split/fontforge-dbg/usr/lib/.debug/libfontforgeexe.so.2.0.0
> packages-split/fontforge-dbg/usr/lib/.debug/libgdraw.so.5.0.0
> packages-split/fontforge-dbg/usr/lib/.debug/libgutils.so.2.0.0
> packages-split/fontforge-dbg/usr/lib/.debug/libgunicode.so.4.0.0
> packages-split/fontforge-dbg/usr/lib/.debug/libgioftp.so.2.0.0
> packages-split/fontforge-dbg/usr/lib/.debug/libfontforge.so.2.0.0
>
> packages-split/fontforge-dbg/usr/lib/python2.7/site-packages/.debug/fontforge.so
> packages-split/fontforge-dbg/usr/lib/python2.7/site-packages/.debug/psMat.so
>
> //Hongxu
>
>
>> Sorry, I didn't get your point :(
>>
>> First, do you mean one dbg package take more image size than sub
>> dbg packages? I am afraid the sub dbg package could not work correctly
>> (see my comments above)
>>
>> Especially only one hardlink of separated debug info file in each
>> directory (see commits `d4eaf42 package.bbclass: only one hardlink
>> of separated debug info file in each directory' in oe-core)
>>
>> Second, does this fix cause dbp package RDEPENDS issue? Or already
>> existed issue? If the former, please paste a reproduce steps, if the
>> latter,
>> as I mentioned above, RP rethinks to improve debug package dependency
>> handling in 2.7 (its too late for 2.6 now.),
>>
>> //Hongxu
>>
Oopps - ${PN}-dbg RDEPENDs on ${PN} (still?) - My thoughts were a bit
upside down :). Sorry for the noise.

Andreas