[cmake-developers] Introducing: message(DEBUG)

Alexander Neundorf neundorf at kde.org
Mon Mar 5 15:59:37 EST 2012


On Monday 05 March 2012, Brad King wrote:
> 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 warning but with "CMake Debug"
> >> as the header instead of "CMake Error" or "CMake Warning".
> > 
> > I would like to have that switchable in some way. E.g. for Boost_DEBUG I
> > don't have stack traces at the moment, but the contents are the
> > information I need. Stacktraces are useful, but not always.
> 
> I'm not opposed to a switch but extra verbosity rarely hurts debug
> output IMO.  

Currently, if you use cmake --debug-output you already get a backtrace for 
each printed message.
So it's maybe not necessary to add them there additionally.

Alex



More information about the cmake-developers mailing list