Yes, BlueZ is one of those libraries which is strangely licensed. libbluetooth.so is GPL licensed.. whereas liba2dp.so is LGPL ... for other libraries.. I guess each individual headers need to be checked...
On Mon, Aug 9, 2010 at 4:33 AM, Madhavi Manchala <[email protected]> wrote: > Dear Atul, > > Thank you very much for your valuable inputs. > > Thanks and Regards, > Madhavi M > > On Aug 7, 7:44 pm, Atul Raut <[email protected]> wrote: >> Hi Madhavi, >> >> If your code is not part of linux kernel then you dont need to worry >> for anything. >> Things to take care is your code should not use any opensource code >> or linked to opensource. If you want to do so you need to make library >> and define your header file which will be opensource and library will >> be propriety >> >> Thanks and Regards >> Atul . >> >> On Fri, Aug 6, 2010 at 9:36 PM, Madhavi Manchala >> <[email protected]>wrote: >> >> >> >> > Dear All, >> >> > I am trying to implement a custom voice codec on the android bluetooth >> > platform by linking it, into the A2DP module. I have heard different >> > versions from different people regarding the licenses (like LGPL and >> > Apache License). So, before starting my work, I would like to know if >> > I would be forced to reveal my source code, once I implement my codec >> > on BlueZ stack. Please let me know, so that I can choose my platform, >> > before starting my work. >> >> > Regards, >> > Madhavi. >> >> > -- >> > unsubscribe: >> > [email protected]<android-porting%2bunsubscr...@googlegroups.com> >> > website:http://groups.google.com/group/android-porting- Hide quoted text - >> >> - Show quoted text - > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- --Pavan Savoy -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
