Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.2.2
-
None
-
-
dcc2704d17 (qt/qtbase/dev) 2f1d1dc5bc (qt/qtbase/6.2) 52a84c2508 (qt/qtbase/6.3) 2f1d1dc5bc (qt/tqtc-qtbase/6.2) 52a84c2508 (qt/tqtc-qtbase/6.3) dcc2704d17 (qt/tqtc-qtbase/dev)
Description
Hi,
CMakeLists.txt in qtbase attempts to look for symlinks and halts if they are found. See the lines:
get_filename_component(build_dir_absolute "${CMAKE_BINARY_DIR}" ABSOLUTE) get_filename_component(build_dir_realpath "${CMAKE_BINARY_DIR}" REALPATH) if(NOT build_dir_absolute STREQUAL build_dir_realpath) message(FATAL_ERROR "The build path \"${CMAKE_BINARY_DIR}\" contains symlinks. \ ...
The problem is that one path can contain 'Qt' and one can contain 'qt'. For example my build failed because one was
/Users/myname/Qt/6.2.2/Src
and the other
/Users/myname/qt/6.2.2/Src
In my situation there are no symlinks present and I had to rename my qt directory to Qt to make the build work; using
mv qt Qt
I don't know why one path would have Qt when the real path was qt, but the renaming worked. A quick search on the Qt Forum shows at least one other user having problems with this symlink check.
Can I suggest making the test case-insensitive OR maybe changing path references (in the build system) to always use qt instead of Qt.
I'm a commercial licensee downloading source through the online installer and then building from source (with some patches applied).