[OE-core] [PATCH 3/3] libpcap: fix PACKAGECONFIG

[Burton, Ross]

On 11 June 2015 at 10:08, Robert Yang <liezhi.yang at windriver.com> wrote:

> The BLUEZ is default to bluez5, but there is only PACKAGECONFIG[bluez4],
> no PACKAGECONFIG[bluez5], and the current version of libpcap (or the
> higher version 1.7.3) only supports bluez4, we can't use
> ${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', '${BLUEZ}', '', d)}
> for PACKAGECONFIG any more since BLUEZ is default to bluez5, and not
> supported, and there is no bluez4 in oe-core any more, set PACKAGECONFIG
> to ""
> by default, other layers where bluez4 is available can enable it via
> bbappend.
>

So the point of this logic is that simply removing bluez5 from
DISTRO_FEATURES results in bluez4 being enabled where relevant, which
you're removing.

Would a better fix would be to have a dummy (empty) bluez5 stanza?

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150615/500acb58/attachment-0002.html>