<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[macOS supported versions]]></title><description><![CDATA[<p dir="auto">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 <code>arm64</code>, I get this warning:</p>
<pre><code>warning: building for macOS-12.0, but linking with dylib '/usr/local/lib/libgvc.7.dylib' which was built for newer version 15.0
</code></pre>
<p dir="auto">I built the dylib myself from GraphViz sources.</p>
<p dir="auto">This warning is somewhat confusing considering the text on the site at <a href="https://doc.qt.io/qt-6/macos.html" target="_blank" rel="noopener noreferrer nofollow ugc">https://doc.qt.io/qt-6/macos.html</a> which seems to imply that macOS 15 is supported?</p>
<p dir="auto">Also, I get the following warning:</p>
<blockquote>
<p dir="auto">Qt has only been tested with version 15 of the platform SDK, you're using 26.<br />
This is an unsupported configuration. You may experience build issues, and by using<br />
the 26.0 SDK you are opting in to new features that Qt has not been prepared for.<br />
Please downgrade the SDK you use to build your app to version 15, or configure<br />
with <strong>CONFIG+=sdk_no_version_check</strong> when running qmake to silence this warning.</p>
</blockquote>
<p dir="auto">I had just upgraded Xcode yesterday, and it messed up something which made <code>clang</code> not find any of the standard STL headers such as <code>&lt;cstdint&gt;, &lt;iostream&gt;</code>, etc. I was able to fix this (I think) by calling</p>
<pre><code># re-install the command-line tools:
sudo xcode-select --install
sudo xcode-select --reset
</code></pre>
<p dir="auto">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.</p>
]]></description><link>https://forum.qt.io/topic/163321/macos-supported-versions</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 23:14:50 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/163321.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 23 Sep 2025 10:37:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to macOS supported versions on Thu, 25 Sep 2025 18:55:35 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/simonschroeder">@<bdi>SimonSchroeder</bdi></a> said in <a href="/post/832018">macOS supported versions</a>:</p>
<blockquote>
<p dir="auto">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.</p>
</blockquote>
<p dir="auto">I think you are right. Also found <a href="https://stackoverflow.com/questions/24243176/how-to-specify-target-mac-os-x-version-using-qmake" target="_blank" rel="noopener noreferrer nofollow ugc">this thread on StackOverflow</a>, and the accepted answer says:</p>
<blockquote>
<p dir="auto">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.</p>
</blockquote>
<p dir="auto">Marking this as solved again.</p>
]]></description><link>https://forum.qt.io/post/832026</link><guid isPermaLink="true">https://forum.qt.io/post/832026</guid><dc:creator><![CDATA[Robert Hairgrove]]></dc:creator><pubDate>Thu, 25 Sep 2025 18:55:35 GMT</pubDate></item><item><title><![CDATA[Reply to macOS supported versions on Thu, 25 Sep 2025 12:21:21 GMT]]></title><description><![CDATA[<p dir="auto">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.</p>
]]></description><link>https://forum.qt.io/post/832018</link><guid isPermaLink="true">https://forum.qt.io/post/832018</guid><dc:creator><![CDATA[SimonSchroeder]]></dc:creator><pubDate>Thu, 25 Sep 2025 12:21:21 GMT</pubDate></item><item><title><![CDATA[Reply to macOS supported versions on Thu, 25 Sep 2025 11:21:29 GMT]]></title><description><![CDATA[<p dir="auto">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.</p>
<p dir="auto">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.</p>
<p dir="auto">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?</p>
<p dir="auto">I think I remember seeing something about doing this in Xcode itself with a <code>-switch</code> command ... I'm not on my MacBook Air at the moment, so I will have to junt for that later.</p>
<p dir="auto">(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+...)</p>
]]></description><link>https://forum.qt.io/post/832014</link><guid isPermaLink="true">https://forum.qt.io/post/832014</guid><dc:creator><![CDATA[Robert Hairgrove]]></dc:creator><pubDate>Thu, 25 Sep 2025 11:21:29 GMT</pubDate></item><item><title><![CDATA[Reply to macOS supported versions on Wed, 24 Sep 2025 09:57:25 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/simonschroeder">@<bdi>SimonSchroeder</bdi></a> Thanks!</p>
]]></description><link>https://forum.qt.io/post/831954</link><guid isPermaLink="true">https://forum.qt.io/post/831954</guid><dc:creator><![CDATA[Robert Hairgrove]]></dc:creator><pubDate>Wed, 24 Sep 2025 09:57:25 GMT</pubDate></item><item><title><![CDATA[Reply to macOS supported versions on Wed, 24 Sep 2025 06:44:49 GMT]]></title><description><![CDATA[<p dir="auto">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).</p>
<p dir="auto">I'm still using qmake. You can select the macOS SDK version by setting <code>QMAKE_MACOSX_DEPLOYMENT_TARGET</code> in qmake projects. I'm not sure what the equivalent is in CMake.</p>
]]></description><link>https://forum.qt.io/post/831950</link><guid isPermaLink="true">https://forum.qt.io/post/831950</guid><dc:creator><![CDATA[SimonSchroeder]]></dc:creator><pubDate>Wed, 24 Sep 2025 06:44:49 GMT</pubDate></item><item><title><![CDATA[Reply to macOS supported versions on Tue, 23 Sep 2025 22:45:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sgaist">@<bdi>SGaist</bdi></a> said in <a href="/post/831930">macOS supported versions</a>:</p>
<blockquote>
<p dir="auto">If memory serves well, you can have multiple SDKs on the same machine that you can switch depending on your development requirements.</p>
</blockquote>
<p dir="auto">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?</p>
]]></description><link>https://forum.qt.io/post/831942</link><guid isPermaLink="true">https://forum.qt.io/post/831942</guid><dc:creator><![CDATA[Robert Hairgrove]]></dc:creator><pubDate>Tue, 23 Sep 2025 22:45:59 GMT</pubDate></item><item><title><![CDATA[Reply to macOS supported versions on Tue, 23 Sep 2025 19:02:20 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">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.</p>
<p dir="auto">As for SDK support, that's normal as well since that release of Qt was made before 26 was released.</p>
<p dir="auto">If memory serves well, you can have multiple SDKs on the same machine that you can switch depending on your development requirements.</p>
]]></description><link>https://forum.qt.io/post/831930</link><guid isPermaLink="true">https://forum.qt.io/post/831930</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Tue, 23 Sep 2025 19:02:20 GMT</pubDate></item></channel></rss>