Open stevenwdv opened 5 months ago
Can confirm, this can be quick-fixed by simply touch
-ing the reported file.
This is probably an error with relative/absolute paths.
I am having a look at this. Apparently the Qt
CMake files are using the CMAKE_TOOLCHAIN_FILE
as a variable, which is not intended behavior, and ignoring the documentation of CMake allows this variable to be a relative path. It could be this needs to be reported to Qt, but I am still having a look for a solution in the recipe if possible.
Describe the bug
Installing
qt
doesn't work anymore with Conan 2.3.0, while with 2.2.3 it works fine.Normally I'd report this with Conan Center, but this is apparently a regression with Conan itself. Although it may still need to be handled at the package level, I don't know.
From my uninformed view, I think that the direct cause may be e11c576beed6493efb54394a3dc5d9ef1cd57db5.
How to reproduce it
Execute
conan install --build=missing --requires=qt/[~6] -c tools.system.package_manager:mode=install -o 'qt/*:with_sqlite3=False' -o 'qt/*:with_pq=False' -o 'qt/*:with_odbc=False' -o 'qt/*:with_brotli=False' -o 'qt/*:with_openal=False' -o 'qt/*:with_md4c=False' -o 'qt/*:with_harfbuzz=False'
(extra options added to minimize install time)Observe error from
QtAutoDetectHelpers.cmake
: