Please file any issues as standalone bugs and link them to this issue.
The work can be roughly grouped into three areas, by increasing priority:
- Making sure x86_64 builds of Qt work when running via Rosetta (QTBUG-86405)
- Making sure single architecture arm64 builds work and run fine
- Enabling universal builds of Qt, building and packaging x86_64 and arm64 together (QTBUG-85447)
The last step is the one requiring the most work, as neither our qmake or CMake build systems are prepared for multi architecture builds. In the interim the user can build Qt twice, their app twice, and then lipo the application binaries into a universal app.
Note: The work for making Qt run well on macOS 11 (Big Sur) is tracked in QTBUG-85546
Building on the DTK should work like a normal Qt for macOS build.
Build Qt for macOS natively first, so that you have the host tools buildt in for example /build/qt/6.0/qtbase. Then in /build/qt/6.0-arm/qtbase
|For Gerrit Dashboard: QTBUG-85279|
|307226,5||Treat -xplatform or -device-option as being a cross compilation||5.15||qt/qtbase||Status: MERGED||+2||0|
|307228,3||Treat -xplatform or -device-option as being a cross compilation||dev||qt/qtbase||Status: MERGED||+2||0|
|307233,3||macOS: Exclude 32-bit builds by checking pointer size||dev||qt/qtbase||Status: MERGED||+2||0|
|307234,3||macOS: Don't assume platform has objc_msgSendSuper_stret||dev||qt/qtbase||Status: MERGED||+2||0|
|307290,2||macOS: Don't assume platform has objc_msgSendSuper_stret||5.15||qt/qtbase||Status: MERGED||+2||0|
|307291,2||macOS: Don't assume platform has objc_msgSendSuper_stret||5.12||qt/qtbase||Status: MERGED||+2||0|
|307292,2||macOS: Exclude 32-bit builds by checking pointer size||5.12||qt/qtbase||Status: MERGED||+2||0|
|307293,2||macOS: Exclude 32-bit builds by checking pointer size||5.15||qt/qtbase||Status: MERGED||+2||0|
|307294,2||Treat -xplatform or -device-option as being a cross compilation||5.12||qt/qtbase||Status: MERGED||+2||0|