[OE-core] [PATCH 00/11] Change all bluez4 references to virtual/bluez

[Otavio Salvador]

Hello Chris,

On Wed, Mar 26, 2014 at 12:40 PM, Chris Larson <clarson at kergoth.com> wrote:
>> Last time I've asked for bluez4->bluez5 upgrade path fix on target I was
>> told that it's not supported and bluez5 isn't drop-in replacement for
>> bluez4 (yet), did that change already?
>
> Afaik libbluetooth is API compatible, but the dbus api isn't. I haven't done
> much runtime testing, though. So I don't think virtual/bluez is an
> appropriate name given they aren't 100% compatible bluetooth implmentations
> across the board. In meta-mentor, we moved to a combination of two
> virtual-runtimes (for flexibility, to facilitate replacement not just with
> bluez5, but also potentially with a third party implementation, two
> virtual-runtimes, one for hardware support, one for the userland bluetooth
> stack, (and potentially others in the future)) with a virtual/libbluetooth
> build virtual, and then you need to ensure obexd/hcidump are left out of the
> build, since they were merged into bluez5.

I did a look in meta-mentor and I think the interesting commit is:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/commit/?id=1444d8b0d3617bea503e498150e558abe5b20114

and a blog post about the API changes:

http://www.bluez.org/bluez-5-api-introduction-and-porting-guide/

and an issue in Fedora, which might help in the migration:

https://fedoraproject.org/wiki/Changes/Bluez5

I don't know if someone is tracking the packages which uses the D-Bus
API of BlueZ to be check if there are available patches for it.


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750