Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-05 Thread Brad King
On 3/3/2012 5:25 AM, Rolf Eike Beer wrote: + else if (*i == DEBUG) +{ ... +status = true; Rather than being a conditional version of STATUS I think full stack information is useful for debugging. Add to the cmake::MessageType enumeration a DEBUG value and teach cmake::IssueMessage

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-05 Thread Rolf Eike Beer
On 3/3/2012 5:25 AM, Rolf Eike Beer wrote: + else if (*i == DEBUG) +{ ... +status = true; Rather than being a conditional version of STATUS I think full stack information is useful for debugging. Add to the cmake::MessageType enumeration a DEBUG value and teach

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-05 Thread Brad King
On 3/5/2012 10:22 AM, Rolf Eike Beer wrote: Rather than being a conditional version of STATUS I think full stack information is useful for debugging. Add to the cmake::MessageType enumeration a DEBUG value and teach cmake::IssueMessage to handle it. The output should look like an error or

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-05 Thread Eric Noulard
2012/3/5 Rolf Eike Beer e...@sf-mail.de: On 3/3/2012 5:25 AM, Rolf Eike Beer wrote: +  else if (*i == DEBUG) +    { ... +    status = true; Rather than being a conditional version of STATUS I think full stack information is useful for debugging.  Add to the cmake::MessageType enumeration

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-05 Thread Eric Noulard
2012/3/5 Brad King brad.k...@kitware.com: On 3/5/2012 10:22 AM, Rolf Eike Beer wrote: Rather than being a conditional version of STATUS I think full stack information is useful for debugging.  Add to the cmake::MessageType enumeration a DEBUG value and teach cmake::IssueMessage to handle it.

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-05 Thread Brad King
On 3/5/2012 10:33 AM, Eric Noulard wrote: 2012/3/5 Brad Kingbrad.k...@kitware.com: Elsewhere in this thread discussion proposed filters on messages based on their context. Filters based on the full backtrace should be possible and would give a lot of control. You mean something like a regex?

[cmake-developers] Introducing: message(DEBUG)

2012-03-03 Thread Rolf Eike Beer
I have a small patch to CMake that looks like this: diff --git a/Source/cmMessageCommand.cxx b/Source/cmMessageCommand.cxx index e1dbf34..ad24368 100644 --- a/Source/cmMessageCommand.cxx +++ b/Source/cmMessageCommand.cxx @@ -52,6 +52,18 @@ bool cmMessageCommand status = true; ++i;

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-03 Thread Yury G. Kudryashov
Rolf Eike Beer wrote: I have a small patch to CMake that looks like this: + if (!this-Makefile-IsOn(CMAKE_DEBUG_MESSAGES)) I propose to print message if one of the following holds: * CMAKE_DEBUG_MESSAGES is true; * CMAKE_DEBUG_MESSAGES_FileName is true, where FileName is

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-03 Thread Rolf Eike Beer
Am Samstag, 3. März 2012, 17:05:11 schrieb Yury G. Kudryashov: Rolf Eike Beer wrote: I have a small patch to CMake that looks like this: + if (!this-Makefile-IsOn(CMAKE_DEBUG_MESSAGES)) I propose to print message if one of the following holds: * CMAKE_DEBUG_MESSAGES is true; *

Re: [cmake-developers] Introducing: message(DEBUG)

2012-03-03 Thread Rolf Eike Beer
I have a small patch to CMake that looks like this: For easier access I pushed the topic debug-messages to stage. I don't guarantee for stability here, so I may force-push at any time. Eike signature.asc Description: This is a digitally signed message part. -- Powered by www.kitware.com