QT VS Tools 2.9.1 rev. 6 bug
-
I was running windeployqt as a "Post-Build Event" step which was set up like this for a Debug build:
call $(QtToolsPath)\qtenv2.bat call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat" $(QtToolsPath)\windeployqt --pdb --debug $(TargetPath)and like this for a Release build:
call $(QtToolsPath)\qtenv2.bat call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat" $(QtToolsPath)\windeployqt $(TargetPath)I noticed that the Qt Project Settings now offers the option to run this with the Run Deployment Tool option, so I turned off my Post-Build Event stuff and set Run Deployment Tool to Yes.
Unfortunately:
1>DeepSkyStacker.vcxproj -> C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe 1>windeployqt: "C:/Qt/5.15.2/msvc2019_64/bin\windeployqt.exe" --list target --dir C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\ C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe 1>Unable to find dependent libraries of C:\Anaconda2\Library\bin\Qt5Widgetsd.dll :Cannot open 'C:/Anaconda2/Library/bin/Qt5Widgetsd.dll': The system cannot find the file specified. 1> 1> 1>C:\Users\amonra\AppData\Local\QtMsBuild\deploy\qtdeploy.targets(283,5): error MSB3073: The command ""C:/Qt/5.15.2/msvc2019_64/bin\windeployqt.exe" --list target --dir C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\ C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe > "x64\Debug\windeployqt.log"" exited with code 1. 1>Done building project "DeepSkyStacker.vcxproj" -- FAILED.Clearly something is amiss - the question is what?
I've reverted to the previous setup for now
D.
-
Hi,
It seems that your environment mixes conda and your standard Qt installation.
Which one did you use to build your application ?
Can you ensure that you do not have a conda environment active at the same time ? Even the base environment. -
I was running windeployqt as a "Post-Build Event" step which was set up like this for a Debug build:
call $(QtToolsPath)\qtenv2.bat call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat" $(QtToolsPath)\windeployqt --pdb --debug $(TargetPath)and like this for a Release build:
call $(QtToolsPath)\qtenv2.bat call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat" $(QtToolsPath)\windeployqt $(TargetPath)I noticed that the Qt Project Settings now offers the option to run this with the Run Deployment Tool option, so I turned off my Post-Build Event stuff and set Run Deployment Tool to Yes.
Unfortunately:
1>DeepSkyStacker.vcxproj -> C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe 1>windeployqt: "C:/Qt/5.15.2/msvc2019_64/bin\windeployqt.exe" --list target --dir C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\ C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe 1>Unable to find dependent libraries of C:\Anaconda2\Library\bin\Qt5Widgetsd.dll :Cannot open 'C:/Anaconda2/Library/bin/Qt5Widgetsd.dll': The system cannot find the file specified. 1> 1> 1>C:\Users\amonra\AppData\Local\QtMsBuild\deploy\qtdeploy.targets(283,5): error MSB3073: The command ""C:/Qt/5.15.2/msvc2019_64/bin\windeployqt.exe" --list target --dir C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\ C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe > "x64\Debug\windeployqt.log"" exited with code 1. 1>Done building project "DeepSkyStacker.vcxproj" -- FAILED.Clearly something is amiss - the question is what?
I've reverted to the previous setup for now
D.
This post is deleted! -
Well that was a bust:
1>windeployqt: "C:/Qt/5.15.2/msvc2019_64/bin\windeployqt.exe" --list target --dir C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\ C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe
1>EXEC : warning : Cannot find Visual Studio installation directory, VCINSTALLDIR is not set.Looking at the defined macros in the project, I beg to differ with the above:

Still not clear why I needed to remove Anaconda - I shouldn't need to do that!
D.
-
I do not know how Anaconda modifies the Windows environment. One thing you should check if possible is whether you have a conda environment activated. Especially the base environment as it can break stuff. On Linux I had issues building Qt because I had it activated.
-
Did you start a visual studio enabled command line ?
-
Then can you try the same from the command line to see if it's something that is related to Visual Studio or if there's something else in your system that might be off.