Hi Thiago, On 7 Oct 2026, at 00:05, Thiago Macieira <[email protected]> wrote:
On Monday, 5 October 2026 02:13:36 Pacific Daylight Time Tor Arne Vestbø via Development wrote: macOS 27 is now out, and is the first release from Apple that drops support for x86_64 hardware. I don't know what hardware Apple still supported, but the Macbooks and Mac Minis I have access to haven't got an OS update past version 15. I think it was the Mac Pro, but I haven't been able to locate one. https://support.apple.com/en-us/122867 Of those, these are the Intel ones: * MacBook Pro (16-inch, 2019) * MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports) * iMac (Retina 5K, 27-inch, 2020) * Mac Pro (2019) We will not drop any macOS x86_64 support from the code itself, so developers can still build Qt themselves if they still need to continue to support x86_64. Indeed, but the issue there is the lack of Xcode update. Because Apple hasn't released an update, I'm still stuck on the Xcode Clang 17 compiler. There will be a time soon when new content for macOS will fail to compile on the older Xcode SDKs. These are to some degree orthogonal issues. We generally require that Qt is built against a recent (if not latest available) SDK, as that allows us to take advantage of new features. Though we sometimes add #if QT_APPLE_SDK_EQUAL_OR_ABOVE(MACOS(26)) checks, since our CI typically lags one Xcode release behind, and hence one SDK version behind. That requirement applies regardless of architecture. Whether you have that Xcode version available to you depends on your hardware. If you have one of the above mentioned Intel Macs you should be able to run Xcode 26.6, which comes with Clang 21: https://en.wikipedia.org/wiki/Xcode#Xcode_26.0_-_27.x_(since_version_number_change)_2 Cross-compiling x86_64 on an Apple Silicon Mac running macOS 27 and Xcode 27 is also an option. So preemptive question: how long will you accept patches and bug reports for this? If you’re talking about x86_64 macOS bug fixes specifically: as long as people are willing to contribute those patches, and we’re confident they will not affect other platforms or architectures negatively, I don’t see any big issue accepting them, for the time being. At some point we obviously have to draw the line and say no, but I can’t say exactly when that will be right now. That said, the amount of x86_64 specific macOS code should be fairly low, and not likely to be a source of bugs, so I don’t expect much of either patches or bug reports. If you’re talking about patches to support building against older SDKs to be able to keep building for x86_64 I will likely be more conservative, since it adds some overhead for the active maintenance of Qt for macOS, but it will need to be considered more closely when and if such a patch appears. Hope that helps. Cheers, Tor Arne
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
