Looks like Qt 5 for iOS uses static linking. But I have commercial, closed source application. I don't want to provide source code, object files, etc. If I got this right, I can't use LGPL version of Qt for iOS development and I need to by commercial one. Right?
Are there any exceptions in LGPL license of Qt for iOS development that allows us to use static linking? On 7/4/2014 11:51 PM, Jake Petroules wrote: > On 2014-07-04, at 04:31 PM, Pavel Mogilevskiy <[email protected]> wrote: > >> Hello everyone! >> >> I would like to ask you if it's possible to submit my Qt >> application for iOS to iOS App Store. I already sent the same question >> to Qt Interests but >> didn't get a 100% answer. Maybe here I will get the full answer. >> >> What are requirements of submitting apps to iOS App Store? Are >> there any restriction? I heard that Apple doesn't allow to submit >> applications that bundle dylibs to iOS App Store? Is this true? >> >> Thanks for any information. >> >> I'm using Qt 5.3.1 LGPL, iOS SDK 7.1. Application has been >> written with Qt Widgets (non QtQuick/QML). >> >> Thanks! >> >> -- >> Best regards, >> Pavel Mogilevskiy mailto:[email protected] >> >> _______________________________________________ >> Development mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/development > > Yes, you can submit your Qt-based application to the iOS App Store, this is > officially supported by Qt. It's true that you cannot use dylibs if you want > your application to run on iOS 7.x or earlier. Future versions of iOS will > lift this restriction. > > Regarding the other requirements/restrictions, please see Apple's > documentation here > https://developer.apple.com/appstore/resources/approval/guidelines.html and > here https://developer.apple.com/app-store/review/ for more information. > > Statically linking LGPL-licensed code such as Qt in your application also has > certain legal requirements. If your application is open source, there is no > step 2. However, if your application is closed source, the LGPL license > dictates that you must provide a way for end users to re-link with a > different version of Qt. Generally you'd fulfill this license requirement by > providing the necessary object files and Makefiles to rebuild your > application. In either case you must also provide attribution that you used > Qt (in your about page or in the documentation somewhere). If these > requirements are not suitable for your application, you may instead purchase > a commercial Qt license from Digia here: http://qt.digia.com/buy/ > > Disclaimer: I am not a lawyer and this is not legal advice. Please contact a > qualified legal professional for more information if necessary. > > I hope this answers your questions. -- Best regards, Pavel Mogilevskiy mailto:[email protected] _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
