On 16 June 2015 at 03:20, Robert Yang wrote:
> After more thoughts, add a dummy PACKAGECONFIG can avoid confusing
> the user, and avoid the warning, so I updated in the repo:
>
Yes, that's what I meant - thanks.
Ross
--
___
Openembedded-core mailing
On 06/16/2015 09:55 AM, Robert Yang wrote:
On 06/15/2015 07:52 PM, Burton, Ross wrote:
On 11 June 2015 at 10:08, Robert Yang mailto:liezhi.y...@windriver.com>> wrote:
The BLUEZ is default to bluez5, but there is only PACKAGECONFIG[bluez4],
no PACKAGECONFIG[bluez5], and the current v
On 06/15/2015 07:52 PM, Burton, Ross wrote:
On 11 June 2015 at 10:08, Robert Yang mailto:liezhi.y...@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
On 11 June 2015 at 10:08, Robert Yang 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', 'blue
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
