User forums > Nightly builds

The 21 November 2015 build (10595) is out.

<< < (4/9) > >>

linuser42:

--- Quote from: jens on December 10, 2015, 06:21:48 am ---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 ?

--- End quote ---

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:

--- Quote from: Scr3amer on December 04, 2015, 12:08:40 am ---The win32 bug screenshots, macros exist, have a value (which implies they are defined) but still grayed ...

--- End quote ---
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:

--- Quote from: Andy356 on December 10, 2015, 01:18:01 pm ---Mine is revision 10611. I ran codeblocks with -v, and I got an error window with the following messages:

--- End quote ---
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page