rx e powerpdf license

[calm_sea]

i need some clarification. I am trying to understand the license terms of the components I use. I can't understand, in particular, if RX and Powerpdf can be used in closed source software.

[kkuba]

You asked an unclear question. I'll try to guess what you mean. Both components are LGPL licensed, probably version 2.1. The license does not include static link exception. The requirements for including the library in the executable code can be found in point 6 of this license.
Generally, you will have to separate this code because you will virus the main application. This can be done via a dll file or by creating a separate executable file.

[calm_sea]

Thank you very much! I have never created a dll. Can I create a dll with lazarus only with the library to link?

[paweld]

The rx component is LGPL licensed with a linking exception, so you can use it in closed-source programs. You just have to remember that if you modify the component code then you have to make it available.

[kkuba]

You are right. There is an error in the description in OPM. There is a static link exception in * .pas files.

[wp]

Since OPM takes the license information from the package description the error originates from there. And in fact, the package rxnew.lpk, for example, lists "LGPL" as license, rather than "LGPL with linking exception".

Please contact the rx author (alextp, he is a forum user) to fix this inaccuracy.