On Friday 04 April 2008, Jiri Gaisler wrote: > Using LGPL does not require you ship your firmware as > object files and link later. My understanding of LGPL > is that you can ship proprietary core linked with LGPL > code, without having to open-source the proprietary > code.
Yes, you don't have to ship your code if you link to a LGPL library. But you have to ship your executable in such a form that the user can create a new version of it if he wants to use a different version of the LGPLd library. This means you don't have to ship source code, but object files or a static library. For desktop-applications this is different, if you link to a LGPL shared library you can just replace the shared library with another version and everything is fine. You can have a look at the LGPL, it is written somewhere, I don't remember the exact words. Alex -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
