Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Qt 5 support for iOS 14 and XCode 12?
Forum Updated to NodeBB v4.3 + New Features

Qt 5 support for iOS 14 and XCode 12?

Scheduled Pinned Locked Moved Solved General and Desktop
7 Posts 2 Posters 893 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • mbruelM Offline
    mbruelM Offline
    mbruel
    wrote on last edited by
    #1

    Hi,
    To publish apps on the Apple Store it's now needed to build with the iOS 14 SDK and XCode 12.
    Are they supported by Qt5? It's not specified in the doc so I didn't give it a try...
    Instead I've set up a new environment on Big Sur with the latest XCode and iOS SDK and then installed Qt v6.1.2.

    It's quite problematic to have to migrate to Qt6. There are compilation issues... Time need to be spent for the port...
    As Qt5 is still widely used and will be for at least the next 2 years, it would be great if it could support the latest iOS sdk.
    Any update on that?

    1 Reply Last reply
    0
    • VRoninV Offline
      VRoninV Offline
      VRonin
      wrote on last edited by
      #2

      I just run the CI for a random project (https://github.com/VSRonin/QXlsx/runs/3485089771) and Qt 5.15.2 seems to work fine using iOS 14 SDK and XCode 12

      Did you try and experience any issue?

      "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
      ~Napoleon Bonaparte

      On a crusade to banish setIndexWidget() from the holy land of Qt

      1 Reply Last reply
      0
      • mbruelM Offline
        mbruelM Offline
        mbruel
        wrote on last edited by
        #3

        Well I'm expecting this documentation to be updated...
        No I didn't try...
        I'm using a VM to build for macOS and iOS and my previous Catalina one wouldn't have space enough to update XCode (and the iOS sdk) so I created a brand new one with more disk space (150GB instead of 80GB) and thus Big Sur and the latest Xcode.
        After hesitating a while I went directly for Qt 6.1.2 feeling that maybe it was Qt "commercial" choice to not support XCode 12 with Qt5 to kind of force people to switch to Qt6...
        Well I'm going to give it a try and install also Qt5.15 (boring I try to keep my VM with a minimal weight...) cause anyway I think I will be stuck with my QML issue....

        1 Reply Last reply
        0
        • mbruelM Offline
          mbruelM Offline
          mbruel
          wrote on last edited by mbruel
          #4

          Ok so I've a brand new VM with Big Sur v11.5.2 and XCode v12.5.1 (12E507) with iOS SDK 14.5.
          I installed Qt v5.15.2 for macOS and iOS.
          I've managed to build and publish my app on the Apple store without any warnings (few troubles for the signing with the need to recreate a certificate and profile but that's Apple complications...)

          When I compile an app for macOS from QtCreator I'm getting those warnings that I guess we can just ignore...

          Project WARNING: Qt has only been tested with version 10.15 of the platform SDK, you're using 11.3.
          Project WARNING: This is an unsupported configuration. You may experience build issues, and by using
          Project WARNING: the 11.3 SDK you are opting in to new features that Qt has not been prepared for.
          Project WARNING: Please downgrade the SDK you use to build your app to version 10.15, or configure
          Project WARNING: with CONFIG+=sdk_no_version_check when running qmake to silence this warning.
          

          So I guess Qt should update its Qt5 for iOS documentation page stating XCode 12 and iOS 14 are supported!
          Who do we need to contact so they do this update? this could avoid others like me that trust the page to switch to Qt6 against their will...

          PS: unfortunately I've issues with USB Network Gate on BigSur and I'm not able to debug my iOS apps anymore on a device but that's not related with Qt, I'm waiting for their support to sort me out (hopefully...)

          PS2 @VRonin : Funny I used Qt Xlsx 0.3 for my last industrial project. Is it easy to switch to your QXlsx fork? The client was concerned we used an unsupported library and strongly suggested us to switch to yours but as we didn't have time and they wouldn't pay for it we didn't...

          VRoninV 1 Reply Last reply
          0
          • mbruelM mbruel

            Ok so I've a brand new VM with Big Sur v11.5.2 and XCode v12.5.1 (12E507) with iOS SDK 14.5.
            I installed Qt v5.15.2 for macOS and iOS.
            I've managed to build and publish my app on the Apple store without any warnings (few troubles for the signing with the need to recreate a certificate and profile but that's Apple complications...)

            When I compile an app for macOS from QtCreator I'm getting those warnings that I guess we can just ignore...

            Project WARNING: Qt has only been tested with version 10.15 of the platform SDK, you're using 11.3.
            Project WARNING: This is an unsupported configuration. You may experience build issues, and by using
            Project WARNING: the 11.3 SDK you are opting in to new features that Qt has not been prepared for.
            Project WARNING: Please downgrade the SDK you use to build your app to version 10.15, or configure
            Project WARNING: with CONFIG+=sdk_no_version_check when running qmake to silence this warning.
            

            So I guess Qt should update its Qt5 for iOS documentation page stating XCode 12 and iOS 14 are supported!
            Who do we need to contact so they do this update? this could avoid others like me that trust the page to switch to Qt6 against their will...

            PS: unfortunately I've issues with USB Network Gate on BigSur and I'm not able to debug my iOS apps anymore on a device but that's not related with Qt, I'm waiting for their support to sort me out (hopefully...)

            PS2 @VRonin : Funny I used Qt Xlsx 0.3 for my last industrial project. Is it easy to switch to your QXlsx fork? The client was concerned we used an unsupported library and strongly suggested us to switch to yours but as we didn't have time and they wouldn't pay for it we didn't...

            VRoninV Offline
            VRoninV Offline
            VRonin
            wrote on last edited by
            #5

            @mbruel said in Qt 5 support for iOS 14 and XCode 12?:

            I installed Qt v5.15.2 for macOS and iOS.

            I'm waiting for their support to sort me out (hopefully...)

            If you have a commercial license you should have access to more recent versions of Qt5, shouldn't you?

            So I guess Qt should update its Qt5 for iOS documentation page stating XCode 12 and iOS 14 are supported!

            They don't even let us access the Qt5 branch of the repo to contribute to it, I doubt they'll ever update that page

            PS2 @VRonin : Funny I used Qt Xlsx 0.3 for my last industrial project. Is it easy to switch to your QXlsx fork? The client was concerned we used an unsupported library and strongly suggested us to switch to yours but as we didn't have time and they wouldn't pay for it we didn't...

            I do not maintain that library, that's a fork I did on the fly, the live repo is https://github.com/QtExcel/QXlsx
            QXlsx was originally a fork of Qt Xlsx but now moved away from it, migration is not hard at all but I doubt it will be source-code compatible.
            Now that .Net is available on Win, MacOS and Linux, my personal view is that using the C++/CLI library provided by microsoft is the best way to go to handle MS Office files

            "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
            ~Napoleon Bonaparte

            On a crusade to banish setIndexWidget() from the holy land of Qt

            mbruelM 1 Reply Last reply
            1
            • VRoninV VRonin

              @mbruel said in Qt 5 support for iOS 14 and XCode 12?:

              I installed Qt v5.15.2 for macOS and iOS.

              I'm waiting for their support to sort me out (hopefully...)

              If you have a commercial license you should have access to more recent versions of Qt5, shouldn't you?

              So I guess Qt should update its Qt5 for iOS documentation page stating XCode 12 and iOS 14 are supported!

              They don't even let us access the Qt5 branch of the repo to contribute to it, I doubt they'll ever update that page

              PS2 @VRonin : Funny I used Qt Xlsx 0.3 for my last industrial project. Is it easy to switch to your QXlsx fork? The client was concerned we used an unsupported library and strongly suggested us to switch to yours but as we didn't have time and they wouldn't pay for it we didn't...

              I do not maintain that library, that's a fork I did on the fly, the live repo is https://github.com/QtExcel/QXlsx
              QXlsx was originally a fork of Qt Xlsx but now moved away from it, migration is not hard at all but I doubt it will be source-code compatible.
              Now that .Net is available on Win, MacOS and Linux, my personal view is that using the C++/CLI library provided by microsoft is the best way to go to handle MS Office files

              mbruelM Offline
              mbruelM Offline
              mbruel
              wrote on last edited by
              #6

              @VRonin said in Qt 5 support for iOS 14 and XCode 12?:

              If you have a commercial license you should have access to more recent versions of Qt5, shouldn't you?

              I don't have a commercial licence, no need. Are you saying that Qt release are available first for those with licence before getting fully exposed? oO

              Now that .Net is available on Win, MacOS and Linux, my personal view is that using the C++/CLI library provided by microsoft is the best way to go to handle MS Office files

              well who would want to install .Net on Mac or Linux? libQt5Xlsx.so.0.3.0 weights a bit less than 1MB and you've a library allowing you perfectly to write spreadsheet in your apps (without macro or formula). Why use something bigger with .Net dependency?

              VRoninV 1 Reply Last reply
              0
              • mbruelM mbruel

                @VRonin said in Qt 5 support for iOS 14 and XCode 12?:

                If you have a commercial license you should have access to more recent versions of Qt5, shouldn't you?

                I don't have a commercial licence, no need. Are you saying that Qt release are available first for those with licence before getting fully exposed? oO

                Now that .Net is available on Win, MacOS and Linux, my personal view is that using the C++/CLI library provided by microsoft is the best way to go to handle MS Office files

                well who would want to install .Net on Mac or Linux? libQt5Xlsx.so.0.3.0 weights a bit less than 1MB and you've a library allowing you perfectly to write spreadsheet in your apps (without macro or formula). Why use something bigger with .Net dependency?

                VRoninV Offline
                VRoninV Offline
                VRonin
                wrote on last edited by
                #7

                @mbruel said in Qt 5 support for iOS 14 and XCode 12?:

                Are you saying that Qt release are available first for those with licence before getting fully exposed?

                Qt5 has been frozen to Qt 5.15.2 for LGPL but it still gets patch updates from the Qt company for commercial license holders

                allowing you perfectly to write spreadsheet in your apps

                I would not say "perfectly". I worked on the project and it is fairly limited in functionality (e.g. there is no way to make a pivot table or add a comment to a cell). It works well to produce basic outputs though, I agree.

                Why use something bigger with .Net dependency?

                With more functionality comes more weight

                "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
                ~Napoleon Bonaparte

                On a crusade to banish setIndexWidget() from the holy land of Qt

                1 Reply Last reply
                0

                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved