Hi Trey, > We are making a BLE only product for embedded system and cannot use the whole bluez package due to lack of resources. We noticed that the BLE specific code (src/shared) is licensed under LGPL and we are trying to leverage the code as a shared library for our proprietary source BLE application, similar to btgatt-server tool. While compiling, we noticed the LPGL code has a dependency with the following header and source files which are licensed as GPL. > > lib/bluetooth.h > lib/hci.h > lib/mgmt..h > lib/uuid.c > lib/uuid.h > src/shared/ad.c > src/shared/ad.h > > Are there plans to make the above files LGPL or LGPL compatible? the src/shared/ad.[ch] is actually a mistake. No code under GPL should have been accepted into src/shared/ directory. That code is intentionally kept LGPL only. > Are there any plans in the future to remove the GPL dependencies from the LGPL code? The lib/uuid.[ch] is pretty old code and not really nicely abstracted in the first place. However it has been used to speed up the development of the GATT support. The plan is actually to replace that with a new implementation src/shared/uuid.[ch] under LGPL that nicely integrates. The other three are just a bunch of defines or structs. However they are kernel defines and structs and should be most likely come directly from the kernel as UAPI. However we have never gotten around it to clean these up. Some of this is part of the old libbluetooth (which is still internally required). We are talking about 13 year old code here. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
