It's good to see that Qt's licensing docs have gotten a bit less FUD-ish, and it's a nice touch that at the bottom they now link to the official GNU FAQs.
However, let's take a look at what the GNU FAQ says about static linking and the LGPL: <https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic> > If you statically link against an LGPLed library, you must also provide your > application in an object (not necessarily source) format, so that a user has > the opportunity to modify the library and relink the application.`` So, it's a common misunderstanding (sometimes a promoted misunderstanding) that your code has to be open source and LGPL if you statically link against an LGPL library. As the FAQ explains, that's not the case: you need to make your proprietary closed source executable available (upon request, or maybe accessible on a public web server, etc.) in a form that can be re-linked with the LGPL library, which your user may have modified and recompiled.
