Since I am getting closer to do something that I will want to deploy, some iOS problems in QT open source licence appear.
Have some questions, tried to put only these more v-play related, I hope maybe I will get some answers 🙂
From what I have read, forums plus this post https://felgo.com/developers/forums/t/qt-licensing, plus Qt blog, now it is not possible to dynamically link Qt in App Store apps.
From what I understand, since iOS8 it is possible to use dynamic linking in App store apps.
The problem is, it not possible yet to use dynamic linking in all Qt modules in open source licenses.
But is looks like it will be possible soon and it is related to this issue https://codereview.qt-project.org/#/c/123023/
So, V-play team, do you think you will start using dynamic linking on iOS devices by default if it is going to be possible(possible I mean with opens source Qt licence)?
Currently, if I want to use LGPLv3 I would need to use static linking in App Store for Qt(what V-play does I think) but this requires me to give, on request, source objects of the app.
What does source objects mean in this context, can I just allow to share binary package of my app compiled with help from extra v-play feature?
3. It looks like there is a hope to use Qt compiler with opens source license.
More here: http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/
Any plans to start using it in v-play by default if this becomes true?
Or maybe there is no point?
Or maybe I miss completely the point.