Closed T-Maxxx closed 7 months ago
Thanks for your report. The Deployment of a debug libraries in a windows platform it is very specific task, so, i am planned to add this feature in to the cqtdeployer 1.5 .
Deploy debug libraries in Windows system allowed at 1.6,
Describe the bug Deployed package misses some debug versions of Qt libraries and adds release versions when it shouldn't.
To Reproduce Steps to reproduce the behavior:
Expected behavior All debug versions of dependend Qt libraries and plugins are copied to "targetDir" like with windeployqt. Release versions should not be attached.
Result Some debug libraries are attached (Qt5Cored, Qt5Guidd, Qt5Networkd, Qt5Widgetsd, qgenericbearerd etc.), some are not (Qt5Svgd, qwindowsd). Release versions of libraries (Qt5Core, Qt5Core, Qt5Gui, Qt5Svg etc.) has been added too.
Desktop (please complete the following information):
Additional context I have to deploy both debug and release configurations (separately of course). I encountered this issue with Qt5Svgd.dll and qwindowsd.dll missing. I'm almost sure it's because of forced release plugins like qgenericbearer.dll, qsvgicon.dll etc. Please look at output - some lines clearly states
XXX.dll ignored by filter d.dll
(I didn't set it to ignore) when debug versions must be used instead (according to windeployqt output). All plugins copied by windeployqt are debug versions which is perfectly fine (IMHO). "targetDir" already contains my app.exe in 'bin' dir and project dependencies in 'lib' dir before invoking cqtdeployer. So all I need is to add Qt libraries to targetDir with next deploy config:Verbose output log: