Hi Frank, On 5 Oct 2026, at 18:17, Frank Osterfeld <[email protected]> wrote:
I unfortunately couldn't find good data on the current Intel/Mac market share, but isn't it a bit too soon? There’s some data here: https://formulae.brew.sh/analytics/homebrew-os-arch-ci/30d/ And brew only provides arm64 bottles for Qt: https://formulae.brew.sh/formula/qt, so they’ve already taken the plunge requiring from-source builds for x86_64 consumers. Qt Creator usage is at around 11/89 percent for x86_64/arm64 respectively in the same time frame. The requirement for x86_64 is the App Store was just dropped last month. macOS Tahoe will get support for several more years (My guess would be 2028). And Qt 6.12 will also get support for several more years. It would be unfortunate if Qt users who still need to support x86_64 would have to stick to 6.12 (in the worst case that it breaks in >= 6.13 and nobody fixes it). Qt 6.12 will get bug fixes, under the normal branch policies (https://contribute.qt-project.org/quips/16). If your product relies on a _feature_ of Qt 6.13, or a bug fix that’s so risky that it doesn’t make it into the 6.12 series, then you have several choices, including back-porting the feature/fix to 6.12, or building Qt 6.13 from source yourself. Is there the option to move macos/Intel to a lower tier with less frequent builds, to reduce the CI load? Possibly, I will need to look into specifics of our hardware capacity to answer that. If so, would you be interested in being the person (one of them) getting the notice email if such a less frequent build job fails? Cheers, Tor Arne On 5. Oct 2026, at 11:13, Tor Arne Vestbø via Development <[email protected]> wrote: Hi all, macOS 27 is now out, and is the first release from Apple that drops support for x86_64 hardware. It is also the last release that supports running x86_64 binaries on Apple Silicon hardware, as macOS 28 will not ship the Rosetta2 translation layer. So the natural point for us to drop macOS x86_64 official support would be 6.13 (dev). In practice this would mean: • arm64 only build of Qt for macOS SDK binary packages • Including Qt for iOS simulator • no CI tests runs on macOS x86_64 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. The amount of macOS-specific x86_64 code is quite small, and we're well covered on general x86_64 test coverage by our other platforms. So this exercise is largely about reducing CI load, on an increasingly aging hardware farm of Intel Macs. Qt 6.12 (which was just released) of course supports both x86_64 and arm64 macOS, shipping a universal Qt for macOS SDK, and will continue to do so for the LTS lifecycle. Please raise any questions or concerns here, thanks! Cheers, Tor Arne -- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
