[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    [OE-core] Why do we allow empty -dev/-dbg packages ?
From:       martin.jansa () gmail ! com (Martin Jansa)
Date:       2013-12-31 9:45:59
Message-ID: 20131231094559.GB3705 () jama
[Download RAW message or body]

On Tue, Dec 31, 2013 at 09:49:21AM +0800, ChenQi wrote:
> Hi All,
> 
> This might be a dummy question, but it has been puzzling me for some 
> time. So if someone could give me some explanation, that would be really 
> appreciated.
> 
> In bitbake.conf, we have:
> ALLOW_EMPTY_${PN}-dev = "1"
> ALLOW_EMPTY_${PN}-dbg = "1"
> 
> That means we allow emtpy -dev/-dbg packages. But what are the benefits 
> of these empty -dev/-dbg packages?

In some cases it's useful to satisfy default dependcencies:
bitbake.conf:RDEPENDS_${PN}-staticdev = "${PN}-dev (= ${EXTENDPKGV})"

and -dev needs ${PN} even when it's empty in some recipes where all
files are split into separate packages
bitbake.conf:RDEPENDS_${PN}-dev = "${PN} (= ${EXTENDPKGV})"

Not sure about -dbg one.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20131231/7e2f1b76/attachment-0001.sig>



[prev in list] [next in list] [prev in thread] [next in thread]