Problem to solve
For example, after building an executable depended upon Qt on Windows, here is a problem I usually face.
If I don't put the bin directory of Qt Kits into PATH environment variable, the system will pop up the error of "lack-of-dll". The solution of it is to copy those dll files that it need into the directory of executables generaeted by us. But it is quite complex for Qt, so we can use windeployqt tool to do so.
Proposal
I suggest that qttools provide a command called Qt: Deploy executable in Command Palette.
And set the configuration of deployment arguments in settings.json.
Further details
The configuration of deployment arguments in settings.json could be like:
{
"qttools.deployqtArgs": {
"executablePath": "${command:cmake.launchTargetPath}"
"windeployqt": [
"--verbose 1"
"--no-translation",
"--no-opengl-sw"
],
"macdeployqt": [],
"androiddeployqt": []
}
}
Problem to solve
For example, after building an executable depended upon Qt on Windows, here is a problem I usually face.
If I don't put the
bindirectory of Qt Kits intoPATHenvironment variable, the system will pop up the error of "lack-of-dll". The solution of it is to copy those dll files that it need into the directory of executables generaeted by us. But it is quite complex for Qt, so we can usewindeployqttool to do so.Proposal
I suggest that qttools provide a command called
Qt: Deploy executablein Command Palette.And set the configuration of deployment arguments in
settings.json.Further details
The configuration of deployment arguments in
settings.jsoncould be like:{ "qttools.deployqtArgs": { "executablePath": "${command:cmake.launchTargetPath}" "windeployqt": [ "--verbose 1" "--no-translation", "--no-opengl-sw" ], "macdeployqt": [], "androiddeployqt": [] } }