Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] Provide Qt: Deploy executable in Command Palette. #71

Open
hwhsu1231 opened this issue Mar 19, 2022 · 1 comment
Open

[feature] Provide Qt: Deploy executable in Command Palette. #71

hwhsu1231 opened this issue Mar 19, 2022 · 1 comment

Comments

@hwhsu1231
Copy link

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": []
  }
}
@tonka3000
Copy link
Owner

@hwhsu1231 Do you would use it for deploy the application or for the development process? For dev scenario it would be better to inject the PATH variable automatically into launch.json. There is a dedicated variable name environment for that. That way it would be automatically done for you without any copy of files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants