7 comments
Comment actions Permalink

Charley, 'message()' output is only produced during project generation phase by CMake (and invisible in CLion). When CLion builds the project, it's already generated and therefore you don't see this messages.
Is there anything particular among the messages you want to see?

0
Comment actions Permalink

Hi

I would like to up-vote this. I would also like to see message() output somewhere.

These messages should be visible both when we initially open a CMake project in CLion and then also when we do the CMakeLists reload from the CMake pane.

I understand most of the values can be check in the CMake cache after the generation phase, but there might be messages informing for example which if clause was taken etc.

Thanks
Martin

0
Comment actions Permalink

Hello,

Second vote-up. I was forced to use message(WARNING ...) to debug a cmake find script, since message(STATUS ...) wasn't visible in the cmake window.

0
Comment actions Permalink

Do you like to have cmake message() output as a static header up to the program output?

0
Comment actions Permalink

Like Anton Makeev stated before, cmake is only ran during project generation. Reloading the CMakeLists.txt file triggers cmake to refresh the current build files. Some of my scripts have custom output like reporting where they found a dependency. This output is not visible in the cmake window.

0
Comment actions Permalink

Thanks for clarification.
CLion has similar problem in bug tracker (CPP-475).

0
Comment actions Permalink

You're right, this is exactly the feature I was looking for. Thank you for linking the issue.

0

Please sign in to leave a comment.