3 ms·

> Apart from Qt, but the licensing issue is a hindrance Qt is LGPLv3, which is really a problem only if you plan to develop embedded software. Sure, there are

> Apart from Qt, but the licensing issue is a hindrance Qt is LGPLv3, which is really a problem only if you plan to develop embedded software. Sure, there are a few GPL v3 modules here and there, but it's mostly very specific stuff (virtual keyboards, Wayland compositors, ...)

NonNefarious 4y ago
How is it not a problem if you want to sell closed-source software? I guess you can dynamically link desktop applications (although I'm not sure how this works in Apple's Mac app store), but you can't do that with mobile apps.
- kevin_thibedeau 4y ago
  You can use LGPL with closed source so long as you provide object files to relink against.
- pjmlp 4y ago
  If you to sell closed-source software be a good boy/girl and give part of the money pile to Qt developers, so that they keep working on Qt.
  - NonNefarious 4y ago
    And I do. I'm just saying that is not operating under GPL.
- jcelerier 4y ago
  LGPL is not about dynamic linking, and there are plenty of LGPL (and even GPL) apps in the Apple, Android, Mac and Windows app stores. Like, Chromium itself is mostly LGPL and it's never an issue for electron apps, why would it be for Qt ones
  - NonNefarious 4y ago
    LGPL IS about dynamic linking if you don't want to release your source. That's the workaround.
    - jcelerier 4y ago
      https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDyn...
- qalmakka 4y ago
  I have never seen anyone statically linking Qt anywhere, even with a commercial license. The main issue is iOS, where it's basically impossible to ship anything (L)GPLv3 on the app store, but that's due to Apple's lock-in policies. Also, JNI requires you to use DLLs/shared objects, so you definitely can use them on Android.
  - jcelerier 4y ago
    > I have never seen anyone statically linking Qt anywhere, even with a commercial license. from a quick grep on my hard drive, Telegram and QBittorrent statically link against Qt on Windows ; my own software also does, on all platforms. I assume there are others.

NonNefarious 4y ago

How is it not a problem if you want to sell closed-source software? I guess you can dynamically link desktop applications (although I'm not sure how this works in Apple's Mac app store), but you can't do that with mobile apps.

kevin_thibedeau 4y ago
You can use LGPL with closed source so long as you provide object files to relink against.
pjmlp 4y ago
If you to sell closed-source software be a good boy/girl and give part of the money pile to Qt developers, so that they keep working on Qt.
- NonNefarious 4y ago
  And I do. I'm just saying that is not operating under GPL.
jcelerier 4y ago
LGPL is not about dynamic linking, and there are plenty of LGPL (and even GPL) apps in the Apple, Android, Mac and Windows app stores. Like, Chromium itself is mostly LGPL and it's never an issue for electron apps, why would it be for Qt ones
- NonNefarious 4y ago
  LGPL IS about dynamic linking if you don't want to release your source. That's the workaround.
  - jcelerier 4y ago
    https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDyn...
qalmakka 4y ago
I have never seen anyone statically linking Qt anywhere, even with a commercial license. The main issue is iOS, where it's basically impossible to ship anything (L)GPLv3 on the app store, but that's due to Apple's lock-in policies. Also, JNI requires you to use DLLs/shared objects, so you definitely can use them on Android.
- jcelerier 4y ago
  > I have never seen anyone statically linking Qt anywhere, even with a commercial license. from a quick grep on my hard drive, Telegram and QBittorrent statically link against Qt on Windows ; my own software also does, on all platforms. I assume there are others.