Custom Widget cannot be added to Qt Designer
-
Hello,
I'm creating a custom widget on Qt6 (MacOS) using Qt Custom Designer Widget wizard. After the build, I copy the .dylib file to Qt Creator plugins/designer folder. When I open Tools -> Form Editor -> About Qt Designer Plugins, I can see my plugin under Failed Plugins with error: Failed to extract plugin meta data from ''.How to solve this issue?
-
Hi,
Start the application from the command line with the QT_DEBUG_PLUGINS environment variable set to 1 to see what is happening with the plugins.
One thing that you can also check: are you using the same Qt version that was used to build Qt Creator ?
-
Hi,
I've got a similar problem, but a different message from Failed Plugins, which also appears in the terminal, when opening with the QT_DEBUG_PLUGINS=1 instruction :
"Die Bibliothek /Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib kann nicht geladen werden: dlopen(/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib, 0x0005): tried: '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' (code signature in <255C318C-B4EC-35B9-837D-7C477BCA7517> '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Volumes/Preboot/Cryptexes/OS/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' (no such file), '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' (code signature in <255C318C-B4EC-35B9-837D-7C477BCA7517> '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs)"
The Qt Widget Designer Version 6.10.1 had been downloaded with the Qt 6.10.1 package that was used to create the plugin. I took the customwidgetplugin from the Qt examples just as a reference. It also happened with Qt 6.9.0 on macOS 15, but the QtCreator showed and handled plugins with its form editor, when the plugins were copied to the plugins/designer directory in the bundle. -
Hi,
I've got a similar problem, but a different message from Failed Plugins, which also appears in the terminal, when opening with the QT_DEBUG_PLUGINS=1 instruction :
"Die Bibliothek /Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib kann nicht geladen werden: dlopen(/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib, 0x0005): tried: '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' (code signature in <255C318C-B4EC-35B9-837D-7C477BCA7517> '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Volumes/Preboot/Cryptexes/OS/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' (no such file), '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' (code signature in <255C318C-B4EC-35B9-837D-7C477BCA7517> '/Users/xusry/Qt/6.10.1/macos/plugins/designer/libcustomwidgetplugin.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs)"
The Qt Widget Designer Version 6.10.1 had been downloaded with the Qt 6.10.1 package that was used to create the plugin. I took the customwidgetplugin from the Qt examples just as a reference. It also happened with Qt 6.9.0 on macOS 15, but the QtCreator showed and handled plugins with its form editor, when the plugins were copied to the plugins/designer directory in the bundle.@oxidator hi and welcome to devnet,
I wonder if something like described in this thread might be needed.
-
Are you using Designer directly or Qt Creator ?
If the former, you only need to build the qttools module and the latter Qt Creator itself.
In any case, I would also recommend checking the bug report system to see if there's already something related to it and if not, open a new issue to raise awarness.
-
Thank you for that hint.
Maybe I'll get it figured out to get a macOS certificate for Xcode, someday, but I just don't want to spend too much effort on this.
... your link to the bug report system has the singular form not as required the plural... (just for the case you will use for other replies) ;-)
