Missing Code::Blocks debug log

[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.

Any help?

WinXP SVN 4767

[Jenna]

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.

[mandrav]

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.

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 .

[Jenna]

This reminds me to add this plugin to autotools builds .

If you do so, can you please also apply patch #2296 to add your "make_dist.script" to autotools and fix two problems with it as described in the patch comment ?

[mandrav]

This reminds me to add this plugin to autotools builds .

If you do so, can you please also apply patch #2296 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 .

[thomas]

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.

[MortenMacFly]

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?!).

[thomas]

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.