Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
None
-
6.5.0 RC
-
None
-
-
07dd0aff8 (master)
Description
After freshly installing Qt 6.5.0 RC below /opt/Qt/ some of the wrapper scripts around commandline tools contain hardcoded paths that are likely coming from the Qt build environment:
$ grep -R -I 'qt.work' /opt/Qt/6.5.0/*/bin/ /opt/Qt/6.5.0/android_arm64_v8a/bin/qtpaths.bat:/Users/qt/work/install/bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_arm64_v8a/bin/qmake6.bat:/Users/qt/work/install/bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_arm64_v8a/bin/qmake.bat:/Users/qt/work/install/bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_arm64_v8a/bin/qtpaths6.bat:/Users/qt/work/install/bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_arm64_v8a/bin/qtpaths6:/Users/qt/work/install/bin/qtpaths6 -qtconf "$script_dir_path/target_qt.conf" $* /opt/Qt/6.5.0/android_arm64_v8a/bin/qmake6:/Users/qt/work/install/bin/qmake6 -qtconf "$script_dir_path/target_qt.conf" $* /opt/Qt/6.5.0/android_armv7/bin/qtpaths.bat:\Users\qt\work\install\bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_armv7/bin/qmake6.bat:\Users\qt\work\install\bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_armv7/bin/qmake.bat:\Users\qt\work\install\bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_armv7/bin/qtpaths6.bat:\Users\qt\work\install\bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_armv7/bin/qtpaths6:\Users\qt\work\install\bin/qtpaths6 -qtconf "$script_dir_path/target_qt.conf" $* /opt/Qt/6.5.0/android_armv7/bin/qmake6:\Users\qt\work\install\bin/qmake6 -qtconf "$script_dir_path/target_qt.conf" $* /opt/Qt/6.5.0/android_x86/bin/qtpaths.bat:/home/qt/work/install/bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86/bin/qmake6.bat:/home/qt/work/install/bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86/bin/qmake.bat:/home/qt/work/install/bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86/bin/qtpaths6.bat:/home/qt/work/install/bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86/bin/qtpaths6:/home/qt/work/install/bin/qtpaths6 -qtconf "$script_dir_path/target_qt.conf" $* /opt/Qt/6.5.0/android_x86/bin/qmake6:/home/qt/work/install/bin/qmake6 -qtconf "$script_dir_path/target_qt.conf" $* /opt/Qt/6.5.0/android_x86_64/bin/qtpaths.bat:/home/qt/work/install/bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86_64/bin/qmake6.bat:/home/qt/work/install/bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86_64/bin/qmake.bat:/home/qt/work/install/bin\qmake6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86_64/bin/qtpaths6.bat:/home/qt/work/install/bin\qtpaths6.exe -qtconf "%~dp0\target_qt.conf" %* /opt/Qt/6.5.0/android_x86_64/bin/qtpaths6:/home/qt/work/install/bin/qtpaths6 -qtconf "$script_dir_path/target_qt.conf" $* /opt/Qt/6.5.0/android_x86_64/bin/qmake6:/home/qt/work/install/bin/qmake6 -qtconf "$script_dir_path/target_qt.conf" $*
The .bat files likely do not matter on Linux but at least the "6"-suffixed forwarder scripts should receive the same treatment as the versionless ones.
See attached qmake for a working case and compare to qmake6
which contains the hardcoded path.