I have been trying to use certain LGPL based libraries. I understand that if it is dynamically linked, there is no problem . I understand that If the library code is changed, then the library source code has to be released. But if a person does a static linking of the library, it is not clear if the source code of the application has to be given.
I searched the internet and got few links.
Should the person need to give the object files of the entire source code ?
Should a person need to give the source or linkable objects files that load the static libraries alone and not the whole closed source code ?
How is the LGPL library upgrade handled if it is statically linked with an application(closed source) ?
Both the GPL and LGPL mandate that if any modifications are made to the GPL/LGPLed code directly should be released under the respective licenses.
I think LGPL is popular compared to GPL because LGPL provides the freedom to link with any project. GPL allows dynamic linking alone. GPL allows static linking but with a condition that the source code that uses the library statically should be placed under GPL :-(.
On continuing my search, i came across the below link -
So, Is static linking of LGPL libraries allowed ? If Yes, How ? Should i need to release any part of the closed source code or library ? Should i need to release the closed source software object files or only the library based object files ? Any ideas ?
Thx in advans, Karthik Balaguru