The 03 November 2018 build (11508) is out.

[damorin]

HI,

I was able to disable it quickly enough before it's stall and now it's working fine.

Thanks

[J.]

The below from the Code::Blocks console when firing this CB nightly on a Win10 machine. Is there anything to worry about, since the message text is prompted in red?

Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\Cccc.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\CppCheck.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\Cscope.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\DoxyBlocks.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\EditorConfig.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\headerfixup.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\ThreadSearch.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\ToolsPlus.zip'.
Manager failed to load XRC resource 'C:\...\portables\CB_20181103\share\codeblocks\wxSmithAui.zip'.

[Miguel Gimenez]

Some plugins don't need XRC resources. Probably the manager should be less verbose, or remark that it is normal behaviour.

[oBFusCATed]

I guess, I should fix this, because people are worried by these messages and they don't do a search before posting, so forum post pile up...

[J.]

Good idea. It is that the manager can raise an error window as well. I have a self-built version here which does that regularly when starting CB which is annoying. Especially, when it is neither an error nor a failure. So I am pretty much with you to fix that. Thanks!

[stahta01]

Some plugins don't need XRC resources. Probably the manager should be less verbose, or remark that it is normal behaviour.

I suggest not defining cb_debug while building CB and the message should go away.

Edit: If the devs want I can create a patch that splits the header that causes the message into something called like cb_assert.h and allow the plugins to define the value of cb_debug instead of the core application.
This would be able to keep the warning for the plugins that need XRC file.

Tim S.
 

[oBFusCATed]

And then the bugs would be hidden... and wxDEBUG/ASSERT is causing the problem not cbDEBUG...