Jonas Maebe wrote:
It doesn't matter whether the products or tools are commercial or not.
The LGPL means that if you link statically against TDBF, you have to
provide (on request) the object files of your program to customers that
bought the original tool so they can relink it against newer/modified
versions of the TDBF code.
There is no reason why you would ever have to release your own source
code, except if you would start mixing your own source code into the
TDBF units or so.
Wikipedia <https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License>
writes
Essentially, if it is a "work that uses the library", then it must be possible for the software to
be linked with a newer version of the LGPL-covered program. The most commonly used method for doing
so is to use "a suitable shared library mechanism for linking". Alternatively, a statically linked
library is allowed if either source code or linkable object files are provided.[2]
The most common solution is to compile LGPL code into a shared/dynamic library.
Regards,
Adriaan van Os
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
