Deploying Qt5 on Windows 7: Too Difficult
-
[quote author="qttester5" date="1377757029"]I have included all of the files and directories mentioned in this thread as well as ALL of the plugins in the mingw directory to be extra safe, and my app also just shows a white screen; in fact I am using an included Qt Quick demo app, the Minehunt application. There is just no way I can get it to actually run correctly in an environment that does not have Qt installed already. It runs fine in Creator. This is so frustrating. No errors, not crashes, just a white screen.[/quote]
what is your grafic card ? have you tested it under other machines ?
-
In my App, I create a dialog QML object dynamically.
When deploying, I found that I had to add
QtQuick-->Controls
The DLL is under a further subdir, "Private"I ended up deploying the whole Controls directory for an added 6MB to the package!
Thanks to the contributors above, I would never have got here without their encouragement.
-
Seems like a headache. For me this works:
- Use Microsoft's free tool "Process Explorer" to get a list of all DLLs used while running the exe in release mode via QT Creator (they can be showed in lower pane)
- Copy all of these to the same directory as the exe, not bothering with adding any subfilders
http://technet.microsoft.com/sv-se/sysinternals/bb896653.aspx
-
See also my answer in the "other post. ":http://qt-project.org/forums/viewthread/30301/P30/#163354
That tool is interesting. Thanks for sharing. ;-)
-
Actually I was a bit optimistic there.. The stand-alone exe ran on my primary PC but only because it had Qt installed, It didn't execute on another PC.
AFAIKT Process Explorer actually does reveal all DLLs used, with path. I did some further investigations on my primary PC by adding DLLs and folders to where Qt put my exe and renaming the folders Qt wants to use until I see in Proc Expl that it uses the ones I want it to, by making use of that Qt gives me an error message when starting the exe from within it with ctrl+R (otherwise it would be hard to guess which folder structre it wants).
A few conclusions from that adventure:
- It often needs more than the DLLs, so when you have identified a DLL it wants, then copy the entire directory with the DLL (you can try to optimize later by deleting files but the non-DLL files are usually very small, and the ones ending with "d" you can skip, they are for debug mode)
- When I rename a folder that Qt wants to use, sometimes it know about an alternate folder. For one group of DLLs, Qt itself took over the DLLs and fetched them in such an alternate folder, so they were no longer under my app in Proc Expl but under Qt, and I had to reboot Qt to stop it from doing that.
The folders imageformats, platforms, QtQuick and QtQuick.2 should be in the exe's folder, together with the rest of the DLLs; eactly which, you clearly see in Proc Expl. Could add screenshot but can't see the forum supports it.
Still doesn't work though. Don't now why, but I'd suspect it's something other than DLLs missing. And I don't have more time for this right now.
PS One DLL you and everybody else seem to require is Qt5V8.dll but it doesn't exist on my PC. Perhaps from an older version?
-
[quote author="DavidGGG" date="1393184567"]Actually I was a bit optimistic there.. The stand-alone exe ran on my primary PC but only because it had Qt installed, It didn't execute on another PC.[/quote]To check a deployment package on your development PC, rename your Qt installation folder. This effectively turns your PC into a Qt-free environment, so when you launch your application it won't use your development DLLs.
[quote]Still doesn't work though. Don't now why, but I'd suspect it's something other than DLLs missing. And I don't have more time for this right now.[/quote]If you use QML, you also need the qmldir files. See http://qt-project.org/wiki/Deploy_an_Application_on_Windows
[quote]PS One DLL you and everybody else seem to require is Qt5V8.dll but it doesn't exist on my PC. Perhaps from an older version?[/quote]V8 is the JavaScript engine used by QML in Qt 5.0 and 5.1. It's no longer used in Qt 5.2.
[quote]Could add screenshot but can't see the forum supports it.[/quote]For now, you'll need to upload it to an external site. The forum can display external images. Anyway, there is a screenshot of the deployment folder at http://qt-project.org/wiki/Deploy_an_Application_on_Windows
-
Qt is absolutely great, fast and easy to develop apps.
But some points in it, for us newbies, are a real problem. One of them is deployment, for example, on Windows.
I had this problem and solved it as I think in a very stupid and simple way, and I want to share it in hope that it can help someone.
After compiling release version of the app, putting the exe file in a separate folder and running, I surely got a long list of messages about missing dlls, which I successfully took in "mingw482_32\bin" folder and put in my app root folder. Also I knew about the need in "bin\plugins\platforms\qwindows.dll" and copied it also. On the dev computer now the app ran OK, but if I started it on another computer, it didn't work. Windows didn't show any warning messages, but the app window did not appear on the screen, app started and was shown in task manager, but not on the screen.
I thought it might be some missing libs or plugins, which the app took from Qt install folder, to test it I renamed Qt installation folder on dev machine and vualia - app didn't work on dev machine either. So it was the point.
But how to find out which plugins the app depends on? There are quite a lot of them. I searched and read a lot on the forum here, I tried Dependancy Walker, MS Process Explorer and windeployqt.exe, all are not good to give results in a fast and comfortable way.
After some hours of headache a stupid idea came to my mind - I just began renaming folders in Qt install folder to make them unavailable for the app. I began from the top level dirs, found the one, the lack of which made my app to stop working, and then proceded to its subdirectories. In 5 minutes I found out that my app needed ..\mingw482_32\qml\QtQuick\Window.2 and qml\QtQuick.2 directories, which I coppied to my app folder like that – myappfolder\QtQuick\Window.2 and myappfolder\QtQuick.2 and it made everything work perfectly.
I understand that this is a really stupid method, but it became a hundred times faster than seaching and learning all those wierd tools which are as far from deployment as stars from earth, imho.
