Including GPL headers in LGPL code [closed]

StackOverflow https://stackoverflow.com/questions/7387799

  •  29-10-2019
  •  | 
  •  

Question

I want to use Bluez Bluetooth (GPL) library in a proprietary C based application. I want to have GPL workaround for using it.

My plan is:

  1. Write an LGPL wrapper library which links to Bluez library (GPL), also includes the Bluez library headers (which also is GPL). Thus the wrapper becomes LGPL (Am I right?).

  2. Link the LGPL wrapper library into my proprietary application.

With this is my proprietary application is safe from GPL contamination?

If not, what is the right workaround here?

Thanks in advance

Was it helpful?

Solution

That is not so easy :-) You cannot get rid of GPL constraints.

I had similar case in my company. The solution we chose was to separate the functionality that requires usage of GPL based library (in my case it was libiw) and write a standalone application that is also GPL based (so we open as little code as possible). Then start the "little program" from our main application (e.g. by fork/execl functions) and communicate with it by signals, pipe or things like RPC. I do not know if it applies to your situation, because I do not know what your application is to do, but it is a workaround that we chose.

OTHER TIPS

No, this is not possible. The GPL requires that the whole application be distributed under GPL. There is no provision for making wrappers to work around it, and certainly no provision under which GPL "decays to" LGPL. (Maybe you're thinking of the other direction - LGPL allows you to relicense as GPL.) What you're looking to do is classic infringement against a GPL'd application and it will almost surely be pursued (assuming you're caught).

The right workaround is either to write your own bluetooth implementation or to distribute your application under the GPL.

Finally, the standard disclaimer applies: I'm not a lawyer. If you cannot read the GPL yourself and determine what I just told you, you really need to hire a lawyer to interpret it for you before you touch any GPL code.

Any such workaround would be against the spirit of the GPL and if the FSF dotted their Is and crossed theit Ts, there shouldn't be any of those.

Your only legal options are (IANAL):

  • do not use the library
  • adhere to the GPL
  • ask the copyright holders for a different license

Please contact a lawyer for professional advise.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top