Priority: P2: Important
Affects Version/s: 6.0.3, 6.1.0 RC, 6.2
Component/s: Build System: CMake
Commits:cc2d45fd72a764312be9757ef96cc9abd5d1b423 (qt/qtquickcontrols2/dev) 2d0133cbcfffeb507a3d4122ecdfdf20b5dee35e (qt/qtquickcontrols2/6.1) 7d141071101e99c57eda9bb89cc91dbf03deaebe (qt/qtquickcontrols2/6.0)
Trying to build the qtquickcontrols2 gallery example on macOS against a static Qt build with CMake fails to link due to duplicate symbols.
This happens because both the qtquickcontrols2 native mac style plugin and the gallery example create a resource with the same name "qmake_immediate" which was generated by pro2cmake when converting pro files.
This is kind of a fundamental issue because we don't insert the target name into the generated resource name and thus there's always a chance for name conflicts in the resource initializer function name. We don't modify the resource name to be unique, because user code might depend on the given resource name.
Thus we have to ensure that at all Qt built targets (qt modules, qt plugins, qt qml plugins) that are built as part of the Qt SDK don't use a resource name that could conflict with user resource names.
|For Gerrit Dashboard: QTBUG-93172|
|345445,3||CMake: Avoid duplicate symbol errors due to a common resource name||dev||qt/qtquickcontrols2||Status: MERGED||+2||0|
|345909,2||CMake: Avoid duplicate symbol errors due to a common resource name||6.1||qt/qtquickcontrols2||Status: MERGED||+2||0|
|345910,2||CMake: Avoid duplicate symbol errors due to a common resource name||6.0||qt/qtquickcontrols2||Status: MERGED||+2||0|