Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
6.2.0 RC2
-
None
-
acde9784cada212ac23efd7027dc7091a45f9abd (qt/qtbase/dev) cd0b711017330146110baee4bd80ac61a1bd55cf (qt/qtbase/6.2)
Description
Sample content:
c:\Qt\6.2.0\wasm_32\bin>type target_qt.conf
[DevicePaths]
Prefix=/Users/qt/work/install/target
[Paths]
Prefix=../
HostPrefix=../../mingw81_64
HostData=../wasm_32
Sysroot=
SysrootifyPrefix=false
TargetSpec=wasm-emscripten
HostSpec=win32-g++
Documentation=../../Docs/Qt-6.2.0
Examples=../../Examples/Qt-6.2.0
Note the DevicePaths Prefix is the Coin provided install prefix.
The last time the code that generates that entry is at https://codereview.qt-project.org/c/qt/qtbase/+/318626/6/cmake/QtQmakeHelpers.cmake#133
DevicePaths are paths as they appear on device.
https://wiki.qt.io/Qmake_properties
From some quick grepping, the only place where mkspecs uses those paths are for rpath resolution, and even then only when relative rpath resolution is disabled, which are not relevant for iOS/Android/WebAssembly, but is relevant for cross-compiled linux qt (e.g. yocto). It might be yocto is patching those already.
Attachments
Issue Links
- relates to
-
QTBUG-101362 target_qt.conf has CI based paths
- Closed