The LGPL license

[KarenA]

I know nothing about licensing stuff as what I don’t do for myself as mostly been for in-house software.

In another thread .someone said LPGL code is usually avoided in proprietary software. That got wondering about how restrictive it was…

To get a simple explanation I checked Wikipedia…

From Wikipedia:

The license requires that only the LGPL software-parts be modifiable by end-users via source code availability. For proprietary software, LGPL-parts are usually in the form of a shared library such as a DLL so that there is a clear separation between the proprietary and LGPL parts. The LGPL is primarily used for software libraries, although it is also used by some stand-alone applications.

So it seems to me the safest way to include LGPL code in proprietary software would be through DLLs and.or Dylibs and access it through declares or through the shells or maybe a plugin as long as all the plugin source was available. That way the end user in theory could change the LGPL code , recompile and so change functionality… Is that correct?

But Wikipedia also says:

although it is also used by some stand-alone applications.

How can that be unless maybe the non LGPL code part are encrypted but still compilable? … Outside of custom software for a client, I can;t seem anyone wanting to do that.

• Karen

[Christian_Schmitz]

LGPL must be separated for people to change it.
This can be a dll or a helper app.