Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.4
-
None
Description
The configure flag
-appstore-compliant``` can be used to produce a Qt build that will target the Mac App Store. <p></p> We currently build the binary packages without this flag, as we assume most users do not target the Mac App Store. <p></p> Ideally we would not need this flag, while still having the possibility to use the techniques we employ when building without the flag, such as using private APIs for workarounds. This would require e.g.: * Guarded use of private symbols, either * dlsym and objc dynamic lookup for usage of private symbols/classes * separate static libraries for private symbol usage, only linked in if app is not targeting App Store * Building Qt with support for multiple shared memory implementations <p></p> For the moment we should document the requirement to build with the -appstore-compliant flag.
Attachments
Issue Links
- depends on
-
QTBUG-107226 Make SystemV vs POSIX shared memory backends a runtime choice
-
- Reported
-
- relates to
-
QTBUG-68124 macOS packages are not AppStore compliant
-
- Closed
-
-
QTBUG-107167 Qt 6.4 not compatible with Mac App Store
-
- Closed
-
-
QTBUG-113993 Provide a project build/run time option for switching on/off appstore-compliant feature
-
- Reported
-
-
QTBUG-106910 QSharedMemory doc should mention that Qt should be configured with "-appstore-compliant"
-
- Closed
-
-
QTBUG-106911 Make Qt configured with "-appstore-compliant" as default
-
- Closed
-
(1 relates to)