The 05 November 2013 build (9435) is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2812_gcc471-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc471-TDM.7z
And the exception handler dll (for better crash reports) : http://prdownload.berlios.de/codeblocks/exchndl_gcc471-TDM.7z

The 05 November 2013 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20131105_rev9435_win32.7z
  - Linux :
   none

Resolved Fixed:

• sdk and src: make more use of nullptr (no functional change)
• Fix problem with line-numbers being shown for newly opened editors, even if the appropriate options is turned off; see: http://forums.codeblocks.org/index.php/topic,18516.msg126649.html#msg126649
• follow the wx's policies by not including windows.h directly, but through a wrapper (thanks stahta01)
• compiler: fix missing flags for ICC under linux

Regressions/Confirmed/Annoying/Common bugs:

[dmoore]

Ubuntu packages (i386 + AMD64 for Precise through Trusty) are available here.

Code

sudo add-apt-repository ppa:damien-moore/codeblocks-nightly
sudo apt-get update
sudo apt-get install codeblocks codeblocks-contrib

Note: If you are using Code::Blocks from Pasgui's repository you will need to uninstall it and disable that repo before adding this one and reinstalling.

Workaround for possible crash related to compiler plugin at start up:
1. Open terminal, run "codeblocks --safe-mode"
2. Plugins -> Manage Plugins -> Compiler plugin -> Enable, then close the dialog
3. Accept all prompts
4. Close codeblocks
5. Start codeblocks as you normally would and everything should work normally.

[Jenna]

As usual:
Debian packages (binaries and sources) for 32-bit and 64-bit systems (stable and testing) can be found in my debian-repo.
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc18, fc19 and fc20) and RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) can be found in my rpm-repo .

[ToApolytoXaos]

first of all, sorry for reporting an older svn revision issue here which is newer, but since yesterday i have been dealing with peculiar behavior on my Debian machine with svn9423.

Below is the crashing report file that just got generated upon opening C::B.

[oBFusCATed]

As far as I can see this log contains no useful information, so please install debug-symbols or rebuild with --enable-debug configure option.

[ToApolytoXaos]

As far as I can see this log contains no useful information, so please install debug-symbols or rebuild with --enable-debug configure option.

I can't compile the latest HEAD :/

Code

In file included from mozilla_chardet/src/nsBig5Prober.cpp:7:0:
../../src/include/mozilla_chardet/xpcom/glue/nsDebug.h:22:19: fatal error: prprf.h: No such file or directory
 #include "prprf.h"
                   ^
compilation terminated.
make[3]: *** [nsBig5Prober.lo] Error 1
make[3]: Leaving directory `/home/stefanos/svn_code/CodeBlocks/src/sdk'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/stefanos/svn_code/CodeBlocks/src/sdk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stefanos/svn_code/CodeBlocks/src'
make: *** [all-recursive] Error 1

UPDATE: LOL, I think it was a typo of mine during compilation procedure. Instead of placing the debug flag in bootstrap, I placed it in configure.

[stahta01]

@killerbot:

I created a patch that speeds up the time it takes to Compile wxContribItems.
I thought at first the use of a wxWidgets Precompiled Header was the cause of the speedup.
But, most of the speedup was because of the cb project changes needed to use the PCH.

I have tested the compiling of the wxContribItems project; but, I have not run-time tested any of it.

http://forums.codeblocks.org/index.php/topic,18523.msg126748.html#msg126748

Tim S.

[oBFusCATed]

UPDATE: LOL, I think it was a typo of mine during compilation procedure. Instead of placing the debug flag in bootstrap, I placed it in configure.

No, it is not ---enable-debug is configure option, but it is broken at the moment.

But anyway, can you try using Jens' packages instead of self building? Self building causes tons of problems if one is not disciplined!

[Jenna]

Fixed in trunk, by undefining DEBUG in nsDebug.h, so we never try to use mozilla's debug-macros.

[ToApolytoXaos]

No, it is not ---enable-debug is configure option, but it is broken at the moment.

Well, believe it or not, with ./bootstrap --help, I saw that I could use it and used it and compiled just fine; time will tell if it's going to be behaving properly though.

But anyway, can you try using Jens' packages instead of self building? Self building causes tons of problems if one is not disciplined!

I have no problems to build an entire machine from scratch! LOL I moved from a masochist world called FreeBSD to Debian and trust me, building a single project like Code::Blocks looks like a game comparing to the one-week compilation procedure on a hyperthreading PC with FreeBSD ports.

[ToApolytoXaos]

Just a note by the way; I think there's an issue with curly brackets completion on both Windows and Linux.

For example, somebody try this on a Linux machine please:

Code

/* Here, highlight val until something; and press { */
if (something) val = something;

/* The code will look afterwards something like the following below: */
{
    if (something) val = something;
}

Now, on Windows it removes the highlighted line and replaces it with the curly brackets which obviously that's not the default behavior.

[Jenna]

No, it is not ---enable-debug is configure option, but it is broken at the moment.

Well, believe it or not, with ./bootstrap --help, I saw that I could use it and used it and compiled just fine; time will tell if it's going to be behaving properly though.

I can't believe you, because the bootstrap-script does not take any arguments.
You can of course add what ever you want, but it's ignored.

--enable-debug is in fact a parameter of the configure-script, and it adds (among others) -DDEBUG to the Makefile's .
ANd this define was also used in mozilla's header.

[ToApolytoXaos]

I can't believe you, because the bootstrap-script does not take any arguments.
You can of course add what ever you want, but it's ignored.

--enable-debug is in fact a parameter of the configure-script, and it adds (among others) -DDEBUG to the Makefile's .
ANd this define was also used in mozilla's header.

Well, indeed you were right. I literally screw things up. I built my system without debug -_-. I just ran through history commands and saw that it was in ./configure --help and not in ./bootstrap --help. I guess i'm too tired for today. I will fix it tomorrow.

Thank you jens for your clarification and for your patience.

cheers.

[MateusMP]

Hi,

I've been using Code Blocks for some time (a few years already...), and really like the program.
So, I'm here to support by reporting some bugs i found recently. (Not sure if they're bugs actually, but they seems like a strange behaviour for me).


Step by Step:
   Open Code Blocks.
   Create a new Project.
   Create a new virtual folder A, drag some files inside it.
   Create a new virtual folder B, drag some files inside it.
   Create a new virtual folder Parent.
   Select folder A, hold shift, click on the LAST file of folder B. Move the selection over the Parent folder.
   
Expected:
   Folders A and B are moved inside the Parent folder.

Problem:
   All the files will be moved inside the folder "Parent", but folder A will be empty and B folder will disappear.

OBS: Also, try this: put A and B inside Parent, and try to take them out following the same steps. All the files will be moved out of the folders, but neither A nor B will be destroyed.

---
Another Bug?:
Using the same project as the previous bug, change something on the project configuration (So it'll need to be saved, moving the files from virtual folders is enough), close Code Blocks.
-> 1º Dialog will ask if you want to save the Workspace, select No.
-> 2º Dialog will ask if you want to save changes to the project, select No.
-> 3º ANOTHER dialog will ask, again, if you want to save changes to the project.
Is that right? Maybe, just a double check?

Tested on 9425 and 9435.

Thanks!

[Alpha]

Just a note by the way; I think there's an issue with curly brackets completion on both Windows and Linux.
[...]

What do you have set for Settings->Editor->Selection brace completion ?