The build system currently adds bitcode compile and link flags on the PlatformCommonInternal target, with the intention that the flags are only added when building Qt itself, so Qt modules, plugins, etc.
For user projects, it's up to the Xcode setting of ENABLE_BITCODE whether user project code should build with bitcode or not.
Currently the internal flags spill out and get forcefully added to user projects, effectively forcing bitcode to always be on for user projects.
The same happens with the -fapplication-extension flags is static build of iOS and macOS.
|For Gerrit Dashboard: QTBUG-95199|
|360096,3||CMake: Fix bitcode linker flags not to be added on iOS||dev||qt/qtbase||Status: MERGED||+2||0|
|360097,4||CMake: Don't propagate -fapplication-extension to user projects||dev||qt/qtbase||Status: MERGED||+2||0|
|360368,2||CMake: Fix bitcode linker flags not to be added on iOS||6.1||qt/qtbase||Status: MERGED||+2||0|
|360369,2||CMake: Fix bitcode linker flags not to be added on iOS||6.2||qt/qtbase||Status: MERGED||+2||0|
|360370,2||CMake: Don't propagate -fapplication-extension to user projects||6.2||qt/qtbase||Status: MERGED||+2||0|