Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.3.0
-
None
-
Windows 10 21H1
Windows 10 SDK 10.0.19041.0
VS2022
-
-
fc16855eaa (qt/qtbase/dev) fc16855eaa (qt/tqtc-qtbase/dev)
Description
Similar to QTBUG-99656, except that the issue persists for static builds with the relocatable feature turned on, and more values seem to be affected.
ALL qmake variables that are not empty and start QT_* (except QT_VERSION) are affected, likely because of the extra bin in QT_INSTALL_PREFIX being propagated to the other values.
Exhaustive List:
- QT_INSTALL_PREFIX
- QT_INSTALL_ARCHDATA
- QT_INSTALL_DATA
- QT_INSTALL_DOCS
- QT_INSTALL_HEADERS
- QT_INSTALL_LIBS
- QT_INSTALL_LIBEXECS
- QT_INSTALL_BINS
- QT_INSTALL_TESTS
- QT_INSTALL_PLUGINS
- QT_INSTALL_QML
- QT_INSTALL_TRANSLATIONS
- QT_INSTALL_EXAMPLES
- QT_INSTALL_DEMOS
- QT_HOST_PREFIX
- QT_HOST_DATA
- QT_HOST_BINS
- QT_HOST_LIBEXECS
- QT_HOST_LIBS
Build is not usable in Qt Creator due to the usual "Qt Version not installed properly" message. Interestingly the build is usable (at least from my one test) via the command line by using 'qt-cmake', though while the dependent build finishes successfully, the resultant lib binaries have not been tested.
The extra 'bin' is not simply always appended to the end. See attachments.
Configure command (with issue):
-prefix S:\dev\Qt\builder/install/qt-6.3.0-win32-msvc-x64-static-debug-and-release -opensource -confirm-license -platform win32-msvc -static -debug-and-release -submodules qtbase,qtimageformats,qtnetworkauth,qtsvg -feature-relocatable -nomake tests -nomake examples -schannel
Attachments
Issue Links
- relates to
-
QTBUG-102981 Consider creating a qt.conf file in the build dir of an app when using a static relocatable Qt
- Open