Qt VS Tools error messages

Perdrix

When building my project (VS2019) I'm getting:

1>Remember to call vcvarsall.bat to complete environment setup!
1>C:\Users\amonra\Documents\GitHub\DSS\x64\Debug\DeepSkyStacker.exe 64 bit, debug executable
1>Adding Qt5Svg for qsvgicond.dll
1>Skipping plugin qtvirtualkeyboardplugind.dll due to disabled dependencies (Qt5Qml Qt5Quick).
1>Skipping plugin qtvirtualkeyboard_hanguld.dll due to disabled dependencies (Qt5Qml Qt5Quick).
1>Skipping plugin qtvirtualkeyboard_openwnnd.dll due to disabled dependencies (Qt5Qml Qt5Quick).
1>Skipping plugin qtvirtualkeyboard_pinyind.dll due to disabled dependencies (Qt5Qml Qt5Quick).
1>Skipping plugin qtvirtualkeyboard_tcimed.dll due to disabled dependencies (Qt5Qml Qt5Quick).
1>Skipping plugin qtvirtualkeyboard_thaid.dll due to disabled dependencies (Qt5Qml Qt5Quick).
1>Direct dependencies: Qt5Core Qt5Gui Qt5Widgets
1>All dependencies   : Qt5Core Qt5Gui Qt5Widgets
1>To be deployed     : Qt5Core Qt5Gui Qt5Svg Qt5Widgets
1>EXEC : warning : Cannot find Visual Studio installation directory, VCINSTALLDIR is not set.

Is there something that I need to do that I haven't done?

Thanks
D.

mrjj

hi
well did you call vcvarsall.bat ?

Perdrix

Where/when should that call be made? I'm using VS Tools with the VS2019 GUI. Is there a config option I need to set? IFAIK, vcvars32/vcvars64/vcvarsall are only used from the command line, not the VS2019 GUI.

mrjj

@Perdrix
Oh I though it was from cmdline.

Try with a clean default project and see if that runs as then we know if
its due to the actual project or something in the setup is not correct.

It does seems to compile the exe so can it run after ?

Perdrix

Looking at the defined macros in VS, VCInstallDir would definitely seem to be set ...

Perdrix

The problem is happening in the "post-Build" stage where this is invoked:

call $(QtToolsPath)\qtenv2.bat
$(QtToolsPath)\windeployqt --pdb --debug $(TargetPath)

VCInstallDir macro IS set.

mrjj

@Perdrix
yes I was kind of suspecting that.

You can try adding a call for
vcvarsall.bat

like the one for qtenv2.bat

and see.

I know it seems like VCInstallDir is set but the warning it gives kinda suggest, it doesn't see it.

Perdrix

I changed the Post-Build step to do this for Release Build:

call $(QtToolsPath)\qtenv2.bat
call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat"
$(QtToolsPath)\windeployqt $(TargetPath)

and this for Debug Build:

call $(QtToolsPath)\qtenv2.bat
call "$(VCInstallDir)Auxiliary\Build\vcvars64.bat"
$(QtToolsPath)\windeployqt --pdb --debug $(TargetPath)

which appears to have silenced the complaints.