Re: [fpc-pascal] TDBF licensing

Adriaan van Os wrote on Wed, 01 Jul 2015: Jonas Maebe wrote: 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

Re: [fpc-pascal] TDBF licensing

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/modif

Re: [fpc-pascal] TDBF licensing

Thanks Jonas for all the information. I'll pass this information on to the person that asked me. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ ___ fpc-pascal maillist - fpc-pasca

Re: [fpc-pascal] TDBF licensing

On 30/06/15 00:09, Graeme Geldenhuys wrote: > Am I correct in understanding that TDBF included with FPC is a LGPL > licensed component, the one that doesn't have the static linking > exception. TDBF originally comes from http://sourceforge.net/projects/tdbf/ and is indeed distributed under the LGP

[fpc-pascal] TDBF licensing

Hi, Am I correct in understanding that TDBF included with FPC is a LGPL licensed component, the one that doesn't have the static linking exception. So I can't use it in any commercial products or tools without being forced to release all my source code? Regards, - Graeme - -- fpGUI Toolkit -