From: Martin Jansa <martin.jansa@gmail.com>
To: ChenQi <Qi.Chen@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Why do we allow empty -dev/-dbg packages ?
Date: Tue, 31 Dec 2013 10:45:59 +0100 [thread overview]
Message-ID: <20131231094559.GB3705@jama> (raw)
In-Reply-To: <52C222A1.6030705@windriver.com>
[-- 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 --]
next prev parent reply other threads:[~2013-12-31 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 1:49 Why do we allow empty -dev/-dbg packages ? ChenQi
2013-12-31 9:45 ` Martin Jansa [this message]
2014-01-02 6:59 ` ChenQi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131231094559.GB3705@jama \
--to=martin.jansa@gmail.com \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox