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
Sometimes a recipe creates CMake module files for internal usage of conan generators, they are not intended to be included directly by consumers projects, only by files generated by conan generators (they are private CMake module files in a sense). Since conan generators use absolute path of these module files thanks to build_modules/cmake_build_modules, populating builddirs is not required for these files and it may even pollutes CMAKE_MODULE_PATH/CMAKE_PREFIX_PATH of consumers through cmake/CMakeToolchain generators (these generators prepend builddirs of all dependencies to CMAKE_MODULE_PATH & CMAKE_PREFIX_PATH).
Therefore, I advice to not display warnings if a folder not in builddirs contains CMake module files which are all listed in build_modules or the new cmake_build_modules property.
I believe that conan-io/conan-center-index#14066 is encountering the issue identified here. Are there plans to update the hook to eliminate this warning? Thanks
Sometimes a recipe creates CMake module files for internal usage of conan generators, they are not intended to be included directly by consumers projects, only by files generated by conan generators (they are private CMake module files in a sense). Since conan generators use absolute path of these module files thanks to
build_modules
/cmake_build_modules
, populatingbuilddirs
is not required for these files and it may even pollutesCMAKE_MODULE_PATH
/CMAKE_PREFIX_PATH
of consumers throughcmake
/CMakeToolchain
generators (these generators prependbuilddirs
of all dependencies toCMAKE_MODULE_PATH
&CMAKE_PREFIX_PATH
).Therefore, I advice to not display warnings if a folder not in
builddirs
contains CMake module files which are all listed inbuild_modules
or the newcmake_build_modules
property.see conan-io/conan-center-index#8869 (comment)
The text was updated successfully, but these errors were encountered: