Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: Pecan on January 10, 2008, 04:41:41 am

Title: Missing Code::Blocks debug log
Post by: Pecan on January 10, 2008, 04:41:41 am

Didn't there used to be a "Code::Blocks debug log" sitting beside the "Code::Blocks Log"?

I can no longer find the place to turn it on.

Any help?

WinXP SVN 4767

(http://img266.imageshack.us/img266/4806/209sc3.png)

Title: Re: Missing Code::Blocks debug log
Post by: Jenna on January 10, 2008, 07:48:06 am

Since some revision (afaik it comes up near the new Logmanager) you have to explicitely start C::B with the "-d" parameter to start the debug-log.
That's no problem if you start it directly (or via Icon), only when started with double-clicking on a file the debug-log does not open.
I don't know if there is a checkbox somewhere in the settings to open the log always (I did not find), or at least a parameter in "default.conf".
If not it should not be so difficult to create a patch for this.

Title: Re: Missing Code::Blocks debug log
Post by: mandrav on January 10, 2008, 09:32:53 am

Quote from: Pecan

Didn't there used to be a "Code::Blocks debug log" sitting beside the "Code::Blocks Log"?

I can no longer find the place to turn it on.

Quote from: jens

Since some revision (afaik it comes up near the new Logmanager) you have to explicitely start C::B with the "-d" parameter to start the debug-log.
That's no problem if you start it directly (or via Icon), only when started with double-clicking on a file the debug-log does not open.
I don't know if there is a checkbox somewhere in the settings to open the log always (I did not find), or at least a parameter in "default.conf".
If not it should not be so difficult to create a patch for this.

Actually, you should use the loghacker plugin. You can change any of the loggers' output target to file, text control, etc.
This reminds me to add this plugin to autotools builds :).

Title: Re: Missing Code::Blocks debug log
Post by: Jenna on January 10, 2008, 10:59:22 am

Quote from: mandrav on January 10, 2008, 09:32:53 am

This reminds me to add this plugin to autotools builds :).

If you do so, can you please also apply patch #2296 (https://developer.berlios.de/patch/?func=detailpatch&patch_id=2296&group_id=5358) to add your "make_dist.script" to autotools and fix two problems with it as described in the patch comment ?

Title: Re: Missing Code::Blocks debug log
Post by: mandrav on January 10, 2008, 11:30:18 am

Quote from: jens on January 10, 2008, 10:59:22 am

Quote from: mandrav on January 10, 2008, 09:32:53 am

This reminds me to add this plugin to autotools builds :).

If you do so, can you please also apply patch #2296 (https://developer.berlios.de/patch/?func=detailpatch&patch_id=2296&group_id=5358) to add your "make_dist.script" to autotools and fix two problems with it as described in the patch comment ?

That was done few minutes ago :).

Title: Re: Missing Code::Blocks debug log
Post by: thomas on January 10, 2008, 12:23:04 pm

Quote from: mandrav on January 10, 2008, 09:32:53 am

Actually, you should use the loghacker plugin. You can change any of the loggers' output target to file, text control, etc.
This reminds me to add this plugin to autotools builds :).

Actually you should not use the LogHacker plugin, and actually it should not be added to the autotools build.

Title: Re: Missing Code::Blocks debug log
Post by: MortenMacFly on January 10, 2008, 02:27:12 pm

Quote from: thomas on January 10, 2008, 12:23:04 pm

Actually you should not use the LogHacker plugin, and actually it should not be added to the autotools build.

...cause IMHO it's not even working (remember our discussion, Thomas?!).

Title: Re: Missing Code::Blocks debug log
Post by: thomas on January 10, 2008, 03:15:18 pm

Of course it's not working, I told you. It's not finished, it's not working, and it's certainly not for use. :)
And if it is put into the autotools build, it will probably break the build.