macOS: Fix CONFIG+=separate_debug_info for custom QMAKE_BUNDLE_EXTENSION
The code that sets up QMAKE_RESOLVED_BUNDLE did not take QMAKE_BUNDLE_EXTENSION into account. The logic is the same as in UnixMakefileGenerator::init(). Fixes: QTBUG-83222 Change-Id: I8fc4f16b399303394f2106e5c1071347ace93d4a Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
This commit is contained in:
parent
2a4e6124ac
commit
12d5608a25
@ -36,7 +36,11 @@ win32 {
|
||||
plugin_target = $$QMAKE_PLUGIN_BUNDLE_NAME
|
||||
else: \
|
||||
plugin_target = $$TARGET
|
||||
QMAKE_RESOLVED_BUNDLE = $${QMAKE_RESOLVED_TARGET}$${plugin_target}.plugin
|
||||
isEmpty(QMAKE_BUNDLE_EXTENSION): \
|
||||
plugin_ext = .plugin
|
||||
else: \
|
||||
plugin_ext = $$QMAKE_BUNDLE_EXTENSION
|
||||
QMAKE_RESOLVED_BUNDLE = $${QMAKE_RESOLVED_TARGET}$${plugin_target}$${plugin_ext}
|
||||
!shallow_bundle: \
|
||||
QMAKE_RESOLVED_TARGET = $${QMAKE_RESOLVED_BUNDLE}/Contents/MacOS/$${TARGET}
|
||||
else: \
|
||||
@ -46,7 +50,11 @@ win32 {
|
||||
framework_target = $$QMAKE_FRAMEWORK_BUNDLE_NAME
|
||||
else: \
|
||||
framework_target = $$TARGET
|
||||
QMAKE_RESOLVED_BUNDLE = $${QMAKE_RESOLVED_TARGET}$${framework_target}.framework
|
||||
isEmpty(QMAKE_BUNDLE_EXTENSION): \
|
||||
framework_ext = .framework
|
||||
else: \
|
||||
framework_ext = $$QMAKE_BUNDLE_EXTENSION
|
||||
QMAKE_RESOLVED_BUNDLE = $${QMAKE_RESOLVED_TARGET}$${framework_target}$${framework_ext}
|
||||
!shallow_bundle {
|
||||
TEMP_VERSION = $$section(VERSION, ., 0, 0)
|
||||
isEmpty(TEMP_VERSION):TEMP_VERSION = A
|
||||
|
Loading…
Reference in New Issue
Block a user