LGPL license question: use LGPL libraries in closed source applications

Hello,

I need an advice for the correct interpretation of the LGPL. Maybe somebody can help:

For a new Delphi component which I am currently developing, I also need some functions which are provided by a third party library. This library is licensed under LGPL (and written in Delphi).

Now I would like to publish a Demo application, which uses my component and this third party library. This Demo should be "closed source".

Do I have to link the third party library dynamically, using a DLL (or a Delphi package), or can I build a single exe application?


The LGPL seems to allow static linking in some cases [1]: "Alternatively, a statically linked library is allowed if either source code or linkable object files are provided." (Wikipedia)

This sounds to me as if the demo application may be released in a single exe if i also provide the source code for the third party library, or a DCU or DLL/BPL file.


But is this interpretation correct?


Many thanks in advance,

Michael Justin

[1] http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License

--
betasoft - Software for Delphi™ and for the Java™ platform
http://www55.pair.com/betasoft/
.

Relevant Pages

  • Re: Open Source - Licensing
    ... I want to port this to windows and convert it to Delphi. ... this I may have to use a few close source Delphi components. ... the core problem clause is that the code under LGPL should be self ... to replace the LGPLed code with a newer version. ...
    (borland.public.delphi.non-technical)
  • Re: Orange County (Southern California) Delphi User Group Meeting Tuesday, March 22nd
    ... > - Delphi consultants, and Delphi consulting companies, where Delphi ... > - Delphi component vendors and producers, ... What if they don't do web programming? ...
    (borland.public.delphi.non-technical)