Question about Qt LGPL license for Android & iOS
-
Hi; We're using Qt 5.x LGPL. We are using just LGPL license modules. So, we're not using only GPL or only commercial modules like Qt Virtual Keyboard, Qt Charts, Qt Data Visualization, etc.. Also we are using BSD-3 license code, MIT license code and Apache 2.0 license code. We never change Qt codes and 3rd party library codes. Also we never use static linking for Qt codes, the all Qt codes are dynamic linking.
I know, this question has already been asked. But everybody says "I'm not a lawyer". What is correct answer for this question? Can we deploy our mobile app to Google Play and AppStore? Thanks.
-
Hi; We're using Qt 5.x LGPL. We are using just LGPL license modules. So, we're not using only GPL or only commercial modules like Qt Virtual Keyboard, Qt Charts, Qt Data Visualization, etc.. Also we are using BSD-3 license code, MIT license code and Apache 2.0 license code. We never change Qt codes and 3rd party library codes. Also we never use static linking for Qt codes, the all Qt codes are dynamic linking.
I know, this question has already been asked. But everybody says "I'm not a lawyer". What is correct answer for this question? Can we deploy our mobile app to Google Play and AppStore? Thanks.
@Ibrahim said in Question about Qt LGPL license for Android & iOS:
I know, this question has already been asked. But everybody says "I'm not a lawyer". What is correct answer for this question? Can we deploy our mobile app to Google Play and AppStore? Thanks.
The correct answer is "ask Qt Company".
The official statements from them say that building for iOS is incompatible with LGPL license - because the build is static. You have to buy commercial one (or startup if you are eligible) or go with GPL.
QtC also claims similar for Google, although here it is not entirely correct (because it is possible to unpack an .apk, at least one that is not signed - like debug packages, I think).
