The windeployqt tool that comes with Qt 5.2
-
Two choices:
1)
open command prompt
execute: C:\Qt\5.3\mingw482_32\bin\qtenv2.bat
execute C:\Qt\5.3\mingw482_32\bin\windeployqt X:/path/to/your/app.exeYou might need to play around with windeployqt parameters if you don't need everything eg. translations, plugins etc.
go to C:\Qt\5.3\mingw482_32\bin
manually copy any dlls you need to X:/path/to/your/app/directory/ -
This post is deleted!
-
@hskoglund - nice catch!
-
This post is deleted!
-
@chris: thanks, I did some compiling/testing of those icu*.dll chaps this summer because of this "bug":https://bugreports.qt-project.org/browse/QTBUG-39640
It won't be fixed, but now that VS2015 is upon us, VS2012 is kind of obsolete anyway :-)
-
This sounds scary to debug if you don't know what to look for. I'm glad it's not me who had to deal with that :P
And yeah, the split in VS2015 will undoubtedly cause some problems for people deploying their apps and looking for that MSVCR140 that is no longer there. -
This post is deleted!
-
Chris Kawa
2) I have actually managed to gather every dll needed, one by one, in order to run my .exe in another Pc not having qt installed. But it took me 20 minutes to delete one by one and my final folder should look like this:
"http://i.imgur.com/wmyXybO.png":http://i.imgur.com/wmyXybO.png- Didn't know i must run the dat from command, a lot of plugins got copied that was not neccesarry for running the .exe... (but they total 4mb) .. Is it for other version of Windows? I mean for example why do i need windowsprintersupport.dll? I don't use any kind of printing functions.. So which method is correct?
hskoglund
I edited my answer, it was icuin52.dll, i copied the error from google. -
If you open qtenv2.bat in a text editor you will see that it just sets the PATH environment variable like I mentioned in one of previous posts. But this change is local to that batch environment so yeah, you need to run it from command prompt, some script or build system. And if you run two command prompts you would need to run it in both. It doesn't propagate (which is good!).
You might not need all the stuff windeployqt copies over. It can't know what's gonna be loaded at runtime so it just plays it safe and copies everything. Just throw out what you don't use. Some can be skipped via command params, type "windeployqt" without params to see help.
As for manual copying - it took me something like 20 minutes the first time too, then about 3 the second time and then I just wrote a .bat that does it for me and it takes me <1 second ever since. Such is coders life ;)
Btw. Do you really use multimedia, webkit, widgets, qml, sensors, positioning and sql all in one app?
-
This post is deleted!
-
I don't think i do :D, but i could not run the .exe file without all of these .dll files
my .pro file is this:
"http://pastebin.com/zGH5RNR5":http://pastebin.com/zGH5RNR5and i guess the important line is
QT += network widgets webkitwidgetsam i doing something wrong?
-
Nah, I'm just asking. I would expect at least Qml and Quick to be not needed since your app seems to be widget based.
Btw. few things strike me in your .pro file:
Qt has its own "macos for os detection":http://qt-project.org/doc/qt-5/qtglobal.html#Macrosx. You don't need those ON_WIN32 and ON_LINUX
Why do you have this: QT += gui-private ? Seems suspicious ;)
-
This post is deleted!
-
Soo... I am the creator of the .pro file posted above.
-
Qml and Quick are needed by webkitwidgets. We have a feature that loads web pages internally and takes snapshots of them. So the whole dependencies tree of webkit widgets is loaded. Is there a way to be more specific of what part of webkit widgets you're interested in so as to throw out the unneeded dependencies?
-
I know about those macros, but using my own has 2 benefits: (a) are shorter and cleaner, one can recognize them under non-Qt code and immediately understand what they're referring to. (b) I can be 101% sure that if gui-private is included then ON_WIN32 is used. With Q_OS_WIN32 I am only 99.9% :D
-
gui-private is used for zip extraction under Windows (that's why it is included only there)
-
-
This post is deleted!
