

- #Q see qt view app for iphone not working ios 12 how to
- #Q see qt view app for iphone not working ios 12 apk
- #Q see qt view app for iphone not working ios 12 install
Most likely all developers were instructed to answer "IANAL, please contact our legal department". It is very dissapointing however to see absolutely no help from people who work in Qt on the LGPL subject. Neither they will touch you if you are a small-near-zero-profit. Qt company does not have resources to scan every application from the App Store if it uses Qt or not. Do not scream you use Qt LGPLv3 on Qt forums, but make sure you have it visible somewhere down in your application's "About" screen.
#Q see qt view app for iphone not working ios 12 how to
Then for every user who installed your application you have to provide instructions on how to replace Qt libraries: Or even better, put all your application code and resources in a separate Qt Quick plugin which will compile in a static library archive (technically just all object files concatenated together) for iOS. How? Provide your object files for the end user to relink. Again, you just need to give the end user the possibility to replace Qt libraries. Many say it is not possible to use LGPLv3 with iOS because of static linking.
#Q see qt view app for iphone not working ios 12 apk
apk file to every user who installed your application with detailed instructions on how to: Remember, the main goal of LGPLv3 is to give the users ability to replace the library and run the modified version of your application on their device. Rooting is not an option, since it doesn't work on every device (and might not be legal). The user can not navigate to C:/Program Files/YourApp and replace Qt libraries, because it's Android. Even though you link dynamically to the Qt libraries, we now have a small problem. Moving to the mobile platforms, starting with Android.

Looks easy, right? The main goal of LGPLv3 is achieved.
#Q see qt view app for iphone not working ios 12 install
When the end users install your application, they can replace Qt libraries in the following way: On the Desktop you can link dynamically to Qt libraries. Suppose you develop an application and want to keep your source code closed. It is available with LGPLv3 license on major Desktop (Windows, OSX, Linux) and mobile (iOS, Android) operating systems. This is very important to understand, dynamic / static / everything else is just distracting. The main point of the LGPLv3 license is that the end users must have the possibility to replace the library with their own modified version. It is the users of your application and the Library authors who care. App Store does not care which license you use.
