From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: ALLOW_EMPTY versus ALLOW_EMPTY_${PN}? a couple clarifications
Date: Sun, 03 Mar 2013 15:56:29 +0000 [thread overview]
Message-ID: <1362326189.4325.27.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1207060832110.13212@oneiric>
On Fri, 2012-07-06 at 09:10 -0400, Robert P. J. Day wrote:
> just trying to clarify the gory details of the ALLOW_EMPTY setting.
> first, across several .bb files, there is a mixture of these two:
>
> ALLOW_EMPTY = "1"
> ALLOW_EMPTY_${PN} = "1"
>
> what's the difference? what does the first one represent if you're
> not specific? does that cover *all* generated packages?
FWIW, a package name should generally be specified. I've just sent a
patch to OE-Core updating the various references.
Cheers,
Richard
next prev parent reply other threads:[~2013-03-03 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 13:10 ALLOW_EMPTY versus ALLOW_EMPTY_${PN}? a couple clarifications Robert P. J. Day
2012-07-06 14:18 ` Marcin Juszkiewicz
2012-07-06 16:51 ` Robert P. J. Day
2013-03-03 15:56 ` Richard Purdie [this message]
2013-03-03 16:15 ` Martin Jansa
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=1362326189.4325.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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