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

Tools (qmlscene, designer, etc.) in vcpkg qt5:x64-windows build crash due to missing dlls #8408

Closed
spindensity opened this issue Sep 30, 2019 · 1 comment · Fixed by #10644
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@spindensity
Copy link

spindensity commented Sep 30, 2019

Describe the bug

Tools (qmlscene, designer, etc) in vcpkg:x64-windows build crashes.

Environment

  • OS: Win10 1903
  • MSVC 2017 15.9.16

To Reproduce

Steps to reproduce the behavior:

  1. vcpkg install qt5:x64-windows;
  2. Run command %VCPKG_ROOT%\installed\x64-windows\tools\qt5\bin\qmlscene.exe --help;, nothing outputs, the program just crashes silently;
  3. Open %VCPKG_ROOT%\installed\x64-windows\tools\qt5\bin directory in file explorer and double click designer.exe, the program crashes due to missing dlls.

Expected behavior

Tools work like them in the official distribution.

@spindensity spindensity changed the title qmlscene in vcpkg qt5:x64-windows build crashes silently Tools (qmlscene, designer, etc.) in vcpkg qt5:x64-windows build crash due to missing dlls Sep 30, 2019
@Neumann-A
Copy link
Contributor

That is a generell problem with how qt is integrated into vcpkg and how vcpkg handles packages. Sry, there is nothing which could be done here to solve the problem.
As far as I remember qmlscene is build by qt5-declarative so you have to use the version in %VCPKG_ROOT%\installed\x64-windows\tools\qt5-declarative\bin\qmlscene.exe. Alternatively, you could add the path %VCPKG_ROOT%\installed\x64-windows\bin to your PATH variable or build qt5 static.

@JackBoosY JackBoosY added the category:port-bug The issue is with a library, which is something the port should already support label Oct 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants