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
and having cmake_find_package generator enabled in conanfile or passed in to conan_cmake_run(), generated Find$package.cmake has a single message() call. Since the bug is essentially here:
Hi, @rasjani Thanks for reporting and thanks for submitting the PR, I agree with you that all the output generated by Conan should be silenced by CONAN_CMAKE_SILENT_OUTPUT variable.
Environment Details (include every applicable attribute)
Steps to reproduce (Include if Applicable)
with cmake-conan at least when issuing following command:
cmake -GNinja -DCONAN_CMAKE_SILENT_OUTPUT $buildpath
and having cmake_find_package generator enabled in conanfile or passed in to conan_cmake_run(), generated Find$package.cmake has a single message() call. Since the bug is essentially here:
https://github.com/conan-io/conan/blob/develop/conans/client/generators/cmake_find_package.py#L9
Same will most likely happen with calling
conan install
too..When cmake 3.17 or never, these could be removed by filtering on the log level but that is not option for everybody.
Logs (Executed commands with output) (Include/Attach if Applicable)
Excessive output like this will be shown when generating build scripts:
The text was updated successfully, but these errors were encountered: