I'm aware that windeployqt is pretty broken and this is why Vcpkg has own qtdeploy.ps1, but I still wish this issues to be fixed one day. There basically few problems with using it:
- First of all there are different binary in debug directory version of libs and I find no good way to find it using
find_program and no matter what paths I specify it's normal tool found. Might be there should be some way to find it or it's probably should be just removed.
- Another problem is that when I try to use it on release build I getting this output:
Qt binaries in D:\DEV\vcpkg\packages\qt5_x86-windows\bin so basically while tool located in installed directory it's still looking for dependencies from packages directory. I could be wrong here, but I guess it's just might not work when Vcpkg is exported.
Surprisingly when I manually open command line, go into D:\DEV\vcpkg\installed\x86-windows\debug\tools\qt5 and run windeployqt.exe from there it works, but when I try to run it using execute_process even with WORKING_DIRECTORY set it's just fail.
I'm aware that
windeployqtis pretty broken and this is why Vcpkg has ownqtdeploy.ps1, but I still wish this issues to be fixed one day. There basically few problems with using it:find_programand no matter what paths I specify it's normal tool found. Might be there should be some way to find it or it's probably should be just removed.Qt binaries in D:\DEV\vcpkg\packages\qt5_x86-windows\binso basically while tool located ininstalleddirectory it's still looking for dependencies frompackagesdirectory. I could be wrong here, but I guess it's just might not work when Vcpkg is exported.Surprisingly when I manually open command line, go into
D:\DEV\vcpkg\installed\x86-windows\debug\tools\qt5and run windeployqt.exe from there it works, but when I try to run it usingexecute_processeven withWORKING_DIRECTORYset it's just fail.