> If you statically link to an LGPL library, then the entire codebase (your code and the library) must be covered under an LGPL compatible license. This isn't

> If you statically link to an LGPL library, then the entire codebase (your code and the library) must be covered under an LGPL compatible license. This isn't right. You can statically link proprietary code to LGPL libraries and the LGPL license does not "infect" your proprietary code. The only thing you have to do if you go this route is ensure that the people receiving your combined work are able to relink any modified version of the LGPL pieces. This can be done, for example, by providing object files for the proprietary pieces and a script to link them to the LGPL pieces, upon request. https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynami...