Hi,
Is there anyone who wrote a library or application using the Bluez
kernel layer without linking to libbluez out there? I have been starting
to write a C++ wrapper as part of a library that's supposed to be
licensed under LGPL which means I can't look nor link nor even take part
of the code of libbluez (which is GPL).
However, I didn't find any documentation that does teaches how to do
that.
As a side note, I'm wondering how libkdebluetooth and Gnome's libbtctl
can claim that they're LGPL while linking to libbluez.
Maybe I'm confused :)
Thanks for reading,
Mickey.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Mickey,
> Is there anyone who wrote a library or application using the Bluez
> kernel layer without linking to libbluez out there? I have been starting
> to write a C++ wrapper as part of a library that's supposed to be
> licensed under LGPL which means I can't look nor link nor even take part
> of the code of libbluez (which is GPL).
>
> However, I didn't find any documentation that does teaches how to do
> that.
and how do you think it is possible to write a library that uses a
kernel interface that is under GPL. We have the bdaddr_t and some other
socket structs that you need to copy. However ask a lawyer about these
legal things.
And btw the Bluetooth library will be re-released under LGPL if I get an
approval from Qualcomm.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Friday, 15. July 2005 21:38, Michael 'Mickey' Lauer wrote:
=2E..
> As a side note, I'm wondering how libkdebluetooth and Gnome's libbtctl
> can claim that they're LGPL while linking to libbluez.
libkbluetooth is GPLed or did I miss something?
libqobex on the other hand is in fact LGPLed. But libqobex alone as source=
=20
does not derive from or use the BlueZ libs. It does once you compile it,=20
which means that the resulting programs must be GPLed. Which they are. And=
=20
besides that I won=C2=B4t care about such details unless as german court co=
mmented=20
on these linking issues. The outcome will be like throwing a dice anyway.
=46red
=2D-=20
=46red Schaettgen
[email protected]
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel