835c54bc19
We normally override the entrypoint to _qt_main_wrapper via the -e flag to the linker, but if a Swift file is added to the Xcode project, Xcode does some magic, building the app as a shared library, and wrapping it with the Swift code into a custom executable. The -e flag will then be a noop when linking our shared library. To work around this we set the custom LD_ENTRY_POINT Xcode build setting, which triggers Xcode to pass -e when linking the wrapper-executable. This works in practice, but produces a warning on the console that the entrypoint is not found, which has been reported as FB16519113. Fixes: QTBUG-133577 Change-Id: I9d8310b39ac5a4900693df55c2e5bfa346c0300a Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io> (cherry picked from commit 430ba7c0f826ee6f91fbfdc861525cb62b8e725c) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 9fbb8e0090a1d8220479e776feae7c9c5bb8493e) |
||
|---|---|---|
| .. | ||
| bitcode.prf | ||
| default_post.prf | ||
| default_pre.prf | ||
| device_destinations.sh | ||
| devices.py | ||
| exclusive_builds_post.prf | ||
| gc_binaries.prf | ||
| resolve_config.prf | ||
| sdk.prf | ||
| testcase.prf | ||
| testcase_targets.prf | ||
| watchos_coretext.prf | ||
| xcodebuild.mk | ||
| xcodebuild.prf | ||