* Why do we allow empty -dev/-dbg packages ?
@ 2013-12-31 1:49 ChenQi
2013-12-31 9:45 ` Martin Jansa
0 siblings, 1 reply; 3+ messages in thread
From: ChenQi @ 2013-12-31 1:49 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org
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?
Best Regards,
Chen Qi
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Why do we allow empty -dev/-dbg packages ?
2013-12-31 1:49 Why do we allow empty -dev/-dbg packages ? ChenQi
@ 2013-12-31 9:45 ` Martin Jansa
2014-01-02 6:59 ` ChenQi
0 siblings, 1 reply; 3+ messages in thread
From: Martin Jansa @ 2013-12-31 9:45 UTC (permalink / raw)
To: ChenQi; +Cc: openembedded-core@lists.openembedded.org
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
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@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Why do we allow empty -dev/-dbg packages ?
2013-12-31 9:45 ` Martin Jansa
@ 2014-01-02 6:59 ` ChenQi
0 siblings, 0 replies; 3+ messages in thread
From: ChenQi @ 2014-01-02 6:59 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core@lists.openembedded.org
On 12/31/2013 05:45 PM, Martin Jansa wrote:
> 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.
>
Hi Martin,
Thanks for your explanation.
If I understand it right, the above two RDEPENDS are the default for
most recipes and are expected to be overridden in some special recipes,
right? For example, if a recipe is separated into several packages, it's
possible that we need to override the RDEPENDS_${PN}-dev.
Here's another question. If a -dev package is empty, does the default
RDEPENDS on "${PN}" still make sense?
Best Regards,
Chen Qi
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-01-02 6:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-31 1:49 Why do we allow empty -dev/-dbg packages ? ChenQi
2013-12-31 9:45 ` Martin Jansa
2014-01-02 6:59 ` ChenQi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox