5 ms·
> Yes. You must also meet your Qt license obligations: either use Qt dynamically-linked dll/so/dylib files under the LGPL, or, purchase a Qt commercial license
by rubymamis 2y ago
> Yes. You must also meet your Qt license obligations: either use Qt dynamically-linked dll/so/dylib files under the LGPL, or, purchase a Qt commercial license for static linking.
There is this misconception that you can't statically link under the LGPL. From my reading (non legal advice), LGPL supports static linking - you just have to release your object files alongside the binary to allow people to link them with different versions of Qt.
- deleted 2y ago[deleted]
- mappu 2y agoI also think that is legal. But if you are required to distribute additional object files, that does somewhat reduce the benefits of static linking - you might as well use dynamic linking in that case. It's also not completely trivial to do this with the Go linker.
- rubymamis 2y ago> But if you are required to distribute additional object files, that does somewhat reduce the benefits of static linking Because of the total increase in size? Maybe one can just share a link from which the object files can be downloaded?
- zerr 2y agoYou are not required to distribute those along with your app. You can just have them available for download separately if anyone needs it. LGPL requirement is the ability of the end user to relink (not recompile) the executable.
- mappu 2y agoYes, that's definitely possible. Note that the LGPL license says any such download must remain available for 3 years. Before GitHub, I used to host my projects on Google Code. After that service shutdown, I'm not comfortable with such a requirement.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]