Is it possible to use LGPL as a library in a commercial product without opening the product code

0 like 0 dislike
5 views
What should be the linking? Necessarily static or dynamic? Do I need to put the text of the LGPL. Read the license itself, based on this response that the LGPL allows dynamic linking to keep your code closed. But want to be safe, therefore, I ask you! Thank you very much, still licenses the moment thin...

And do I understand correctly that the GPL can't avoid to use it in some form, but not to open their codes? Or anyone have any ideas? Thank you!
by | 5 views

3 Answers

0 like 0 dislike
As I understand it, the LGPL with the linking must be dynamic (so the user could, if desired, to replace the library), the license must be included, and will need to specify where the source code of the library either include a written commitment to provide them on request.
\r
With the GPL, all code should be under GPL and the code to open need to (or as above to give a pledge). Usually pay attention to what code you are obliged to open only to those with whom you are bound by the terms of the license, that is to whom you deliver the finished product.
by
0 like 0 dislike
Linking is necessarily dynamic. In fact, the publication shall be subject to the code of those modules which are written using LGPL code. Static linking embeds the code directly in the module, therefore, also falls into this category.
\r
GPL can be used in closed projects, if the relationship between the components takes place not by loading into the address space of the process and, for example, run the GPL-program as a separate process and communicate with it via pipes. There is only another subtle point regarding the proliferation of such combination product: GPL-program cannot be combined in one package with the proprietary unless it is aggregate (a set of separate, interrelated software packages with which users can work independently; for example, selection for publication on CD). But the difference between two separate programs and one program consisting of two parts, often too subtle and uncertain.
\r
I recommend reading the GPL FAQ.
by
0 like 0 dislike
So, to summarize. In order not to open their codes we:
\r
1) Use the LGPL for dynamic linking
2) Use a separate app on any (?) licenses and interact with them as an external app
3) you can use GPL in closed projects, if the relationship between the components takes place not by loading into the address space of the process and, for example, run the GPL-program as a separate process and communicate with it via pipes.
4) Use the BSD license
\r
if wrong please correct, thanks!
by
110,608 questions
257,186 answers
0 comments
28,804 users