Author Topic: The 03 November 2018 build (11508) is out.  (Read 24041 times)

Offline damorin

  • Multiple posting newcomer
  • *
  • Posts: 52
Re: The 03 November 2018 build (11508) is out.
« Reply #15 on: November 12, 2018, 09:02:30 pm »
HI,

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

Thanks
One problem at a time and we will get there.

Offline J.

  • Multiple posting newcomer
  • *
  • Posts: 47
Startup: Manager failed to load some XRC resources
« Reply #16 on: November 13, 2018, 06:58:53 pm »
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?
Quote
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'.


Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1553
Re: The 03 November 2018 build (11508) is out.
« Reply #17 on: November 13, 2018, 07:09:07 pm »
Some plugins don't need XRC resources. Probably the manager should be less verbose, or remark that it is normal behaviour.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: The 03 November 2018 build (11508) is out.
« Reply #18 on: November 13, 2018, 07:40:50 pm »
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...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline J.

  • Multiple posting newcomer
  • *
  • Posts: 47
Re: The 03 November 2018 build (11508) is out.
« Reply #19 on: November 13, 2018, 07:44:59 pm »
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!

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7582
    • My Best Post
Re: The 03 November 2018 build (11508) is out.
« Reply #20 on: November 13, 2018, 08:14:57 pm »
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.
 
« Last Edit: November 13, 2018, 08:19:29 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: The 03 November 2018 build (11508) is out.
« Reply #21 on: November 13, 2018, 08:19:57 pm »
And then the bugs would be hidden... and wxDEBUG/ASSERT is causing the problem not cbDEBUG...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]