Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. macOS supported versions
Qt 6.12 LTS is out! See what's new in the release blog

macOS supported versions

Scheduled Pinned Locked Moved Solved General and Desktop
8 Posts 3 Posters 3.5k Views 3 Watching
  • 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.
  • R Offline
    R Offline
    Robert Hairgrove
    wrote on last edited by Robert Hairgrove
    #1

    I'm working on a brand-new MacBook Air running Sequoia 15.7 and Xcode which uses version 26 of the macOS SDK. When I build my app in Qt Creator 17.0.1 using Qt 6.9.2 for arm64, I get this warning:

    warning: building for macOS-12.0, but linking with dylib '/usr/local/lib/libgvc.7.dylib' which was built for newer version 15.0
    

    I built the dylib myself from GraphViz sources.

    This warning is somewhat confusing considering the text on the site at https://doc.qt.io/qt-6/macos.html which seems to imply that macOS 15 is supported?

    Also, I get the following warning:

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

    I had just upgraded Xcode yesterday, and it messed up something which made clang not find any of the standard STL headers such as <cstdint>, <iostream>, etc. I was able to fix this (I think) by calling

    # re-install the command-line tools:
    sudo xcode-select --install
    sudo xcode-select --reset
    

    Does anyone know when we can expect SDK version 26 to be officially supported? So far, everything seems to be working, but I am not too optimistic considering these warnings.

    1 Reply Last reply
    1
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      AFAIK, the first warning comes from differences between the target of each build artifacts. One was built to run on 12 while the other on 15.

      As for SDK support, that's normal as well since that release of Qt was made before 26 was released.

      If memory serves well, you can have multiple SDKs on the same machine that you can switch depending on your development requirements.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      R 1 Reply Last reply
      1
      • SGaistS SGaist

        Hi,

        AFAIK, the first warning comes from differences between the target of each build artifacts. One was built to run on 12 while the other on 15.

        As for SDK support, that's normal as well since that release of Qt was made before 26 was released.

        If memory serves well, you can have multiple SDKs on the same machine that you can switch depending on your development requirements.

        R Offline
        R Offline
        Robert Hairgrove
        wrote on last edited by
        #3

        @SGaist said in macOS supported versions:

        If memory serves well, you can have multiple SDKs on the same machine that you can switch depending on your development requirements.

        Thanks ... this would be a great solution! Do you know if the different SDK's must be installed separately, or can one choose by setting some kind of flag in the build process?

        1 Reply Last reply
        0
        • S Offline
          S Offline
          SimonSchroeder
          wrote on last edited by
          #4

          The problem is that new versions of Xcode always delete older versions of the macOS SDK. Just google "download macOS SDK" and you'll find some links to get just the SDK. In most cases it is wise to link against an older SDK so that more people can use your app (I'm not sure why Apple is making this very hard).

          I'm still using qmake. You can select the macOS SDK version by setting QMAKE_MACOSX_DEPLOYMENT_TARGET in qmake projects. I'm not sure what the equivalent is in CMake.

          R 1 Reply Last reply
          3
          • S SimonSchroeder

            The problem is that new versions of Xcode always delete older versions of the macOS SDK. Just google "download macOS SDK" and you'll find some links to get just the SDK. In most cases it is wise to link against an older SDK so that more people can use your app (I'm not sure why Apple is making this very hard).

            I'm still using qmake. You can select the macOS SDK version by setting QMAKE_MACOSX_DEPLOYMENT_TARGET in qmake projects. I'm not sure what the equivalent is in CMake.

            R Offline
            R Offline
            Robert Hairgrove
            wrote on last edited by
            #5

            @SimonSchroeder Thanks!

            1 Reply Last reply
            0
            • R Robert Hairgrove has marked this topic as solved on
            • R Offline
              R Offline
              Robert Hairgrove
              wrote on last edited by Robert Hairgrove
              #6

              Another related question: I was able to extract an older 15.0 SDK from an older Xcode app which can be downloaded from the Apple Developer site and install it parallel to my current Xcode's SDK.

              But does this mean that I need to rebuild the shared libraries for GraphViz and Xerces-C++ which I had previously built using the default SDK (26) that comes with the current version of Xcode? After all, Qt is already built with the SDK 15, and the problem is that the shared libraries were built against SDK 26.

              Xerces-C++ builds with CMake and has nothing to do with Qt; GraphViz builds with autotools, and I am not enabling any features in GraphViz that depend on Qt. I assume that I would have to add some custom flags to build these. Does anyone know what I might have to do to get this to work?

              I think I remember seeing something about doing this in Xcode itself with a -switch command ... I'm not on my MacBook Air at the moment, so I will have to junt for that later.

              (EDIT: This wil be quite a bit of work for GraphViz since I will now have to rebuild all of the dependencies for that which are about 20 different packages, most of them part of GTK+...)

              1 Reply Last reply
              0
              • R Robert Hairgrove has marked this topic as unsolved on
              • S Offline
                S Offline
                SimonSchroeder
                wrote on last edited by
                #7

                I'm not sure what the SDK actually includes. It might be that even the C and C++ runtime libraries are included in the SDK. At least GTK+ will use something from the SDK (just as Qt does). It is very likely that you need to recompile everything.

                R 1 Reply Last reply
                1
                • S SimonSchroeder

                  I'm not sure what the SDK actually includes. It might be that even the C and C++ runtime libraries are included in the SDK. At least GTK+ will use something from the SDK (just as Qt does). It is very likely that you need to recompile everything.

                  R Offline
                  R Offline
                  Robert Hairgrove
                  wrote on last edited by
                  #8

                  @SimonSchroeder said in macOS supported versions:

                  I'm not sure what the SDK actually includes. It might be that even the C and C++ runtime libraries are included in the SDK. At least GTK+ will use something from the SDK (just as Qt does). It is very likely that you need to recompile everything.

                  I think you are right. Also found this thread on StackOverflow, and the accepted answer says:

                  if you build any other libraries that you include in your application bundle, make sure they're also compiled for backwards compatibility! In case it helps with any libraries, there's an equivalent CMake command as well, CMAKE_OSX_DEPLOYMENT TARGET.

                  Marking this as solved again.

                  1 Reply Last reply
                  0
                  • R Robert Hairgrove has marked this topic as solved on

                  • Login

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