Details
-
Bug
-
Resolution: Invalid
-
Not Evaluated
-
None
-
3.2.0
-
None
Description
I've built Installer-framework with OpenSSL, which was linked statically, so I expect, that any binary OpenSSL libs were included in the Installer-framework binaries and isn't required now. But, when I try to run, for example, 'binarycreator.exe" (or any executable I've built) it still doesn't want to run if the path to the OpenSSL binaries aren't set to the PATH variable. I've built Qt with the following configure options:
configure.bat -release -opensource -confirm-license -nomake examples -nomake tests -accessibility -no-qml-debug -no-icu -mp -static -no-sql-sqlite -openssl-linked -static-runtime "OPENSSL_LIBS=-llibssl -llibcrypto -lUser32 -lWs2_32 -lAdvapi32 -lCrypt32" -I D:\Programs\OpenSSL\include -L D:\Programs\OpenSSL\lib -platform win32-msvc -prefix D:/Builds/qt-from-source/qtsdk/packaging-tools/qt-bld/qtbase
The problem is that OpenSSL, probably, won't be installed on the end-user's computer and if I create the installer with this Installer-framework build, the end-user won't be able to run it. Maybe I've done something wrong or, maybe it's a bug?
OpenSSL v. 1_1_1g; Qt 5.12.7, Installer-framework 3.2