CMake part is too verbose

Aleix aleixpol at
Wed Nov 7 23:36:51 UTC 2007

That's completely true, but I didn't want to shut it down until I had tested
it enough. It is very useful in most buggy cases.

What I want to do is to let warnings and errors to output but status
information could get shut up.

Yes, having a preprocessor define to check it is a proper solution, I'll
check it ASAP. Meanwhile, if you want to test it, you just have to shut down
the 9032 from kdebugdialog.


On Nov 7, 2007 11:50 PM, Andreas Pakulat <apaku at> wrote:

> Hi,
> I just killed kdevelop4 started from inside kdevelop3 because it didn't
> manager to load the kdevelop4 source project. The reason is that the
> CMake part outputs so many messages the application outputview can't
> print them all fast enough.
> As far as I can see the output is mainly from the cmake parser and
> visitors and is pretty verbose. Would it be possible to use a custom
> define to output these or not? The kate guys did something like that for
> their highlighting engine.
> I mean the visitor output really is only useful when a parser problem
> exists, OTOH shutting off all of cmake output might hide other problems
> in the cmake manager plugin...
> Andreas
> --
> You have the body of a 19 year old.  Please return it before it gets
> wrinkled.
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the KDevelop-devel mailing list