On 07/16/2013 08:26 AM, Cristian Iorga wrote:
This sets of patches adds bluez5 recipes as experimental packages.
BlueZ 5.X is not an upgrade for Bluez 4.x, as such, no upgrade is
provided/possible.
The two versions of the BT stack also conflicts each other.
In V4 RREPLACES is removed from the recipes.
Cristian Iorga (2):
bluez5: new package for v5.7
bluez4: conflicts with bluez5
meta/recipes-connectivity/bluez/bluez4_4.101.bb | 2 +
.../bluez5/bluez5-5.7/bluetooth.conf | 16 +++++
meta/recipes-connectivity/bluez5/bluez5.inc | 68 ++++++++++++++++++++
meta/recipes-connectivity/bluez5/bluez5_5.7.bb | 5 ++
4 files changed, 91 insertions(+)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5-5.7/bluetooth.conf
create mode 100644 meta/recipes-connectivity/bluez5/bluez5.inc
create mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.7.bb
Have both recipes in a world build causes the following WARNING:
NOTE: multiple providers are available for runtime
libasound-module-bluez (bluez4, bluez5)
NOTE: consider defining a PREFERRED_PROVIDER entry to match
libasound-module-bluez
You can add a line in meta/conf/distro/include/default-providers.inc
Sau!
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core