-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] CMake Generator QUIET behaviour and message types. #9959
Comments
1 task
Merged
praetorian20
added a commit
to praetorian20/conan
that referenced
this issue
Jan 24, 2023
Conan packages using the CMakeDeps generator will now stop printing status messages if the QUIET argument is passed to the respective find_package() CMake call. Fixes conan-io#9959 Fixes conan-io#10857
praetorian20
added a commit
to praetorian20/conan
that referenced
this issue
Jan 24, 2023
Conan packages using the CMakeDeps generator will now stop printing status messages if the QUIET argument is passed to the respective find_package() CMake call. Fixes conan-io#9959 Fixes conan-io#10857
praetorian20
added a commit
to praetorian20/conan
that referenced
this issue
Jan 25, 2023
Conan packages using the CMakeDeps generator will now stop printing status messages if the QUIET argument is passed to the respective find_package() CMake call. Fixes conan-io#9959 Fixes conan-io#10857
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
find_package(<pkg> QUIET)
should not print (informational) message (unless it could not be found...). However both cmake_find_package as well as CMakeDeps generators still print output even on success.E.g.
find_package(libsystemd REQUIRED QUIET)
results in:I found CONAN_CMAKE_SILENT_OUTPUT which silences the output, but my question is if "QUIET" should not already do that.
I.e.
conan_message(FATAL_ERROR [...]
will result in amessage([...]
Environment Details (include every applicable attribute)
The text was updated successfully, but these errors were encountered: