13.09.2016, 21:33, "Jake Petroules" <[email protected]>: > Because the APIs are deprecated by Apple so they would have had to be > removed/changed soon anyways, especially when an alternative (which is the > default now) is already available.
AFAIK they cannot remove API from released SDK, and users may choose to use it even if it's not latest and greatest anymore. > Also it caused build failure on tvOS/watchOS. > >> On Sep 13, 2016, at 11:25 AM, Thiago Macieira <[email protected]> >> wrote: >> >> The changelog contains this entry: >> >> - [QTBUG-45031] The NSURLConnection backend of QNetworkAccessManager has >> been removed, since SecureTransport is the default SSL backend on iOS >> and is enabled by default. This means that building with -no-openssl >> -no-securetransport will no longer provide SSL capabilities on iOS. >> >> WTH? Why are we removing options in a patch release? What happened? >> >> Is the backend so severely broken that it needed to be removed? >> -- >> Thiago Macieira - thiago.macieira (AT) intel.com >> Software Architect - Intel Open Source Technology Center >> >> _______________________________________________ >> Development mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/development > > -- > Jake Petroules - [email protected] > Consulting Services Engineer - The Qt Company > Qbs build tool evangelist - qbs.io > , > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development -- Regards, Konstantin _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
