The 21 November 2015 build (10595) is out.

[linuser42]

Which revision is it ? 10611 ?
I will look into it as soon as possible.
Can you start C::B from a console with the -v switch, to get a more meaningful error-message ?

For me it's rev 10613 from https://launchpad.net/~damien-moore/+archive/ubuntu/codeblocks, on Ubuntu MATE 15.10 64 bit.

I started CB from the console with the -v, and got an additional pop up message

"libwxmathplot.so: cannot open shared object file: No such file or directory"

[Andy356]

Mine is revision 10611. I ran codeblocks with -v, and I got an error window with the following messages:

17:35:10: Cannot load resources from 'memory:ThreadSearch.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:wxSmithAui.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:headerfixup.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:CppCheck.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:Cscope.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:Valgrind.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:DoxyBlocks.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:Cccc.zip#zip:*.xrc'.
17:35:11: Cannot load resources from 'memory:ToolsPlus.zip#zip:*.xrc'.
17:35:11: libwxmathplot.so: cannot open shared object file: No such file or directory
17:35:12: Cannot load resources from 'memory:EditorConfig.zip#zip:*.xrc'.

As a separate issue, I also ran into a glitch after compiling gcc 5.3.0 from source (I had 5.2.0 installed earlier) and selecting it in codeblocks. In the compiler options, I had the c++14 flag enabled, yet I got the 'c++0x_warning.h' error which tells me to enable c++11. Even enabling c++11 doesn't get rid of the message. How I got it to work: I ticked one flag (c++11/c++14) and then in 'other options', I wrote down the other flag, after which codeblocks prompts me to enable it. This causes BOTH the flags to be enabled (otherwise the flags are mutually exclusive) and then the compiler works.

[ollydbg]

The win32 bug screenshots, macros exist, have a value (which implies they are defined) but still grayed ...

Hi, Scr3amer, I need to tell you that the "grayed" feature is not connect to the CC plugin. The former is implemented inside the scintilla control. There is a method we can supply the macros to scintilla control, so it can "gray" the code correctly, but it was not implemented yet. Also, there is a plugin called semantic hightlight, it has the features you like.

[MortenMacFly]

Mine is revision 10611. I ran codeblocks with -v, and I got an error window with the following messages:

Did you forget to run the update script?

[Andy356]

If you're referring to the package manager, 10611 is the latest revision available, from Jens' Debian repo in both the stable and testing pools (I just checked). Otherwise I don't know what you mean by update script.

[Jenna]

If you're referring to the package manager, 10611 is the latest revision available, from Jens' Debian repo in both the stable and testing pools (I just checked). Otherwise I don't know what you mean by update script.

I currently compile a version where this should be fixed.
As workaround, you can install the codeblocks-wxcontrib-dev-package.
Or wait for the new build (will need about two hours on my vserver, because I have to build four versions of C::B on limited resources).

[jsybeyond]

Hello, I want to learn about python. Can I wirte python codes on CB? And can I build and run python on CB?（Uh, maybe I should learn more about English.）

[Jenna]

If you're referring to the package manager, 10611 is the latest revision available, from Jens' Debian repo in both the stable and testing pools (I just checked). Otherwise I don't know what you mean by update script.

I currently compile a version where this should be fixed.
As workaround, you can install the codeblocks-wxcontrib-dev-package.
Or wait for the new build (will need about two hours on my vserver, because I have to build four versions of C::B on limited resources).

10621 for Debian and Fedora/Redhat/CentOS is out and should (now really)  work without the dev-packages.

[ollydbg]

Hello, I want to learn about python. Can I wirte python codes on CB? And can I build and run python on CB?（Uh, maybe I should learn more about English.）

write Python is OK in the editor of C::B, and please note there is a Python plugin which gives more IDE like features. See:
Python plugin - CodeBlocks

[jsybeyond]

Hello, I want to learn about python. Can I wirte python codes on CB? And can I build and run python on CB?（Uh, maybe I should learn more about English.）

write Python is OK in the editor of C::B, and please note there is a Python plugin which gives more IDE like features. See:
Python plugin - CodeBlocks

Uh, how can I download and use it?

[Andy356]

Thanks a lot! Mine just updated to revision 10621 and ran smoothly, just like before. Back to business. B|

On the other hand, the compiler options issue with gcc 5.3.0 is still present. I can't figure out whether it's a Codeblocks bug or something I did. The only thing I did differently from gcc 5.2.0, was adding --prefix=/opt instead of letting it default to /usr/local.

[ollydbg]

Hello, I want to learn about python. Can I wirte python codes on CB? And can I build and run python on CB?（Uh, maybe I should learn more about English.）

write Python is OK in the editor of C::B, and please note there is a Python plugin which gives more IDE like features. See:
Python plugin - CodeBlocks

Uh, how can I download and use it?

I don't know, I haven't used that. You should asked in that thread or you may build this plugin yourself under your OS.

[linuser42]

Everything works for me too after update (now 10623).

[CuteAlien]

Could be another problem of me being on Debian (wx3.0 etc), but just in case - it seems F2 is no longer working correct. It hides the logs window but I can no longer shows it. For that I have to use the menu now. Not certain when this started (sry, hadn't used c::b for a while).

[oBFusCATed]

I confirm this issue. You have to be in an editor for F2 to not work.
Can you post a ticket on sf.net about it?