On Thu, Apr 25, 2013 at 7:12 AM, Phil Blundell <[email protected]> wrote:
> > Something like IMAGE_FEATURES += "dbg-pkgs" should trigger the addition
> > of dbg packages.
>
> I've somewhat belatedly gotten around to using this and encountered a
> couple of issuettes:
>
> 1. There was a spurious-looking RRECOMMENDS_${PN}-dbg in bitbake.conf
> which was causing ${PN} to be dragged into the image whenever ${PN}-dbg
> was installed. This is undesirable because it means that, for example,
> any image which includes sysvinit-pidof will end up installing sysvinit
> and this might cause quite drastic changes to the behaviour of the
> resulting image.
>
> 2. Having fixed the above I'm now left with a couple of file conflicts
> in the -dbg packages. For example, sysvinit and util-linux both
> ship /sbin/sulogin and so sysvinit-dbg and util-linux-dbg both want to
> install /sbin/.debug/sulogin. This is unfortunate if you have an image
> which uses, say, sysvinit-pidof and util-linux-blkid.
>
> I'm not quite sure what the right way to fix (2) is. I suppose in an
> ideal world the -dbg packages would be separated in the same way the
> parent binary packages are, but that doesn't look entirely
> straightforward to arrange.
I had implemented something along these lines back in oe classic, when I
was at MontaVista. See
http://git.openembedded.org/openembedded/tree/classes/package_dbg.bbclass for
that implementation. I haven't touched it or tried using it in some time,
however.
--
Christopher Larson
clarson at kergoth dot com
Senior Software Engineer, Mentor Graphics
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
