You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment find_program() paths are defined in conan_toolchain.cmake, so they will not work with cmake-conan integration.
They are intended for tool_requires, but also if tool_requires do not have find_package() in many cases, what would be the possibilities?
We could parse the output json and inject the respective paths in CMAKE_PROGRAM_PATHS, like conan_toolchain.cmake does, but someone should call conan install in the first place, and I am not sure we can rely on a random find_package() of another dependency for this.
At the moment
find_program()
paths are defined inconan_toolchain.cmake
, so they will not work withcmake-conan
integration.They are intended for
tool_requires
, but also iftool_requires
do not havefind_package()
in many cases, what would be the possibilities?We could parse the output json and inject the respective paths in CMAKE_PROGRAM_PATHS, like
conan_toolchain.cmake
does, but someone should callconan install
in the first place, and I am not sure we can rely on a randomfind_package()
of another dependency for this.cc/ @rollebolle
The text was updated successfully, but these errors were encountered: