26 May 2022
27 May 2022
Cristián 🥑For commercial products, you need a commercial license, like you would normally do with qt/c++ applications
Not if you only use LGPL parts of Qt and follow the LGPL, I think?
Replymessage unavailable
Ссылка
click to show
click to show
I saw this talk in QtDay in Italy in 2019. I don't know if can apply to Qt6/PySide6 yet.
I think yes starting from 6.3 but not sure:
https://www.qt.io/licensing/open-source-lgpl-obligations
Replymessage unavailable
Some Qt modules are only available under GPL, not LGPL: https://doc.qt.io/qt-6/qtmodules.html#gpl-licensed-addons
FreyaNot if you only use LGPL parts of Qt and follow the LGPL, I think?
LGPL has provisions that indicate that any code that is statically linked with a library needs to also be licensed LGPL (or maybe LGPL compatible - sharing the sources), but if you link with a piece of LGPL licensed code dynamically, then your code doesn't need to be LGPL licensed...
How does that work with Python?
Keith KyzivatLGPL has provisions that indicate that any code that is statically linked with a library needs to also be licensed LGPL (or maybe LGPL compatible - sharing the sources), but if you link with a piece of LGPL licensed code dynamically, then your code doesn't need to be LGPL licensed...
How does that
Well surely it's not statically linked... Not a lawyer, but as long as it's possible for users to replace, should be fine
Yes, the situation is far from clear, and also for GPL modules that usually are "bounded" in the same c++ executable.
For example, what about a QML module (VirtualKeyboard or Charts...) that I use in my application without modification? It is on the filesystem, not linked to my application, just used. Is still forbidden to use in closed source?
28 May 2022