Otherwise, the shared libraries of the compiler runtime are used. In the case of release builds using Microsoft Visual C++, these consist of the Visual C++ Redistributable Packages, which are intended for recursive installation by the application's installer on the target machine. In case Qt was built with the configure switch -relocatable turned off, windeployqt replaces the hardcoded local paths in Qt6Core.dll by relative ones.įor Windows desktop applications, the required runtime files for the compiler are also copied to the deployable folder by default (unless the option -no-compiler-runtime is specified). Identified dependencies are then copied to the executable's directory. If a directory is passed with the -qmldir argument, windeployqt uses the qmlimportscanner tool to scan QML files inside the directory for QML import dependencies. exe file as an argument, and scans the executable for dependencies. exe file or a directory that contains an. When using Qt Installer, the script QTDIR/bin/qtenv2.bat should be used to set it up.
It needs to be run within the build environment in order to function correctly. The tool can be found in QTDIR/bin/windeployqt. It creates an installation tree for Windows desktop applications, which can be easily bundled into an installation package. The Windows deployment tool windeployqt is designed to automate the process of creating a deployable folder containing the Qt-related dependencies (libraries, QML imports, plugins, and translations) required to run the application from that folder. We refer to the Plug & Paint example application through out the document to demonstrate the deployment process. This documentation describes deployment process for Windows.
0 kommentar(er)
