In one of the lessons of the Qt it has already been shown how to collect all the DLL, used in the project for the training program for use on other PCs running Microsoft Windows, and now propose to get acquainted with the utility that comes with Qt. This utility is called windeployqt and is a console application, which usually comes bundled with compiler MinGW or MSVC .
To use windeployqt must run from the console, passing as an argument the path to the compiled executable file. Then windeployqt gather all the necessary libraries in the folder where the executable file is located.
The windeployqt utility located in the bin folder, which in turn is located in the folder of the compiler for Qt. Thus, the path to the folder can be as follows:
- MinGW - C:\QT\5.5\mingw492_32\bin\windeployqt.exe
- MSVC - C:\QT\5.5\msvc2013\bin\windeployqt.exe
Work with windeployqt
Now get to work with windeployqt . Let's say you already have a compiled executable file and you need to collect all the required DLL for his work. To do this, we'll do a little preparation and perekinem executable file in the folder prepared for collection. I use to demonstrate EColor project, which is written using MinGW . The executable project file will be placed in the following path D:\EColor\EColor.exe.
After that, it will be necessary to open the console (cmd), and go to the console in a folder with windeployqt . Then run the utility by passing its path or file location, as shown in the following figure.
Then the utility will collect all the necessary work for the executable file DLL. And it will look as follows.
Possible mistakes
Also worth noting is that not everything can go smoothly. For example, windeployqt, can not find the library gcc compiler and give the following error:
Cannot find GCC installation directory. g++.exe must be in the system path.
It is fixed with the prescription in the path environment variable to the bin folder, which contains the GCC and the appropriate library.
To do this, go to the following direction (example for OS Windows 7 ):
Control Panel / System / Advanced System Settings / Environment Variables
Then add in the PATH system variables, which are prescribed path to GCC and its libraries. In my case it looks like this:
- Variable name: PATH
- Variable value: D:\AndroidQT\QT\5.5\mingw492_32\bin;D:\AndroidQT\QT\Tools\mingw492_32\bin;%PATH%
Then I recommend to restart the PC. After that, the error must be an abyss, and the corresponding library will have to catch up in the folder with the executable file.
The files that can not be collected windeployqt
Also, some files can not be collected via windeployqt , that should also take into account and test the application on another PC before release.
For example, during collecting DLL for EColor, windeployqt still missed the following files:
- LIBEAY32.dll
- MSVCP90.dll
- MSVCR90.dll
- MSVCR120.dll
- ssleay32.dll
If the project using QML
UPD 19.11.2018 by alex_lip :
If the project uses QML, then you need to add a special directive --qmldir
This directive will have to specify where to get the source of QML.
windeployqt --qmldir f:\myApp\sources f:\build-myApp\myApp.exe
Добавьте в статью, что если используется Qml следует делать так -
For windeployqt there is the option
--qmldir.Спасибо, добавил
Тук-тук. Привет из прошлого! Не могли бы вы подробнее расказать о том, куда должна быть записана данная вставка "windeployqt --qmldir f:\myApp\sources f:\build-myApp\myApp.exe"? Я пробовал указать после пути распаковки .dll, но получаю ошибку.
f:\build-myApp\myApp.exe - это путь к .exe файлку, который я хочу открыть, я так понимаю, а первый что означает (f:\myApp\sources)? Это папка с релизом проекта или это папка с самим проектом (там где .pro-файл)? Заранее спасибо
By assisting you in losing water weight, Anavar increases the chances of you losing even more weight priligy where to buy Creatinine was measured by use of a colorimetric assay BioSystems SA