The 12.11 RC2 (23 November 2012 build 8598) 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 23 November 2012 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20121123_rev8598_win32.7z
  - Linux :
   none

Resolved Fixed:

• fix translation issues for other languages than English (please don't put too much intelligence in wordings, it may break i18n)
• fix issue with multiple display, as described here: http://forums.codeblocks.org/index.php/topic,17038.msg116770.html#msg116770
• wxSmith: don't allow to unsplit the "Resource" tab (otherwise it cannot be split anymore and it doesn't make sense anyways)
• general clean-up of wxSmith dialogs (no functional change!)
• wxsSizerParentQP: compute checkbox for "border all" correctly
• encoding detector: improved detection of files that contain 0x00 (its more correct now and reads until 0x00 at least)
• applied (modified) patch #3371: EditorTweaks: Fix bug #18795
• debugger: fixed "Cannot find bounds of current function" issue (debugger cannot be stopped after a Step() resulting in that message)
• CC: fixed crash bug described here: http://forums.codeblocks.org/index.php/topic,17115.0.html
• CC: fixed images shown wrong sometimes in symbol browser
• applied patch by Alpha to remove some annoyance in EditorTweaks plugin
• applied patch #3374: SpellCheck: fix tooltip on Linux
• applied patch #3375: CC: handle local scope
• GDB: attempt to fix bug described here: http://forums.codeblocks.org/index.php/topic,17114.0.html
• fix bug #18791: "Multiple matches" message when "find declaration" used
• SFML wizard: make it more generic

Regressions/Confirmed/Annoying/Common bugs:

[Alpha]

• applied patch by Alpha to remove some annoyance in EditorTweaks plugin

As a warning, the annoyance may have been removed, but the position buffering settings are not loaded until the settings window is opened (at least once) due to a missing initialization.

[MortenMacFly]

As a warning, the annoyance may have been removed, but the position buffering settings are not loaded until the settings window is opened (at least once) due to a missing initialization.

Done in trunk.

[shurick]

Packages for openSUSE 12.1, openSUSE 12.2 (binaries and sources) for 32-bit and 64-bit.

[Jenna]

As usual:
Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo.
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc16, fc17 and fc18) can be found in my rpm-repo .
Packages for CentOS/RedHat 5 and 6 can be found there too.

The revision in my repos is 8599, that covers the latest fix described some posts above.

[Folco]

Thanks Jens ! Thanks the whole CB team !!!

[Sphere]

Greetings, and thanks for another awesome nightly.

I was wondering about some default behaviour when creating a new wxWidgets project using the provided templates.

1st Iteration:

I created a new frame-based wxWidgets (2.8.x) project from the new projects menu with wxSmith as the preferred GUI builder. For the advanced "wxWidgets Library Settings" options, I chose "Use default wxWidgets configuration".
In this case both release and debug builds built out of the box.

2nd Iteration:

In this case I did the same as above, but for the advanced "wxWidgets Library Settings" options, I chose "Use Advanced options" with the dynamic and unicode checkboxes both checked. In this case only the release build buildt successfully and the debug build failed with the error message "wx/app.h: No such file or directory". It turned out that I did not have the debug build of wxWidgets installed so I installed it, and then both builds built successfully. But that made me wonder why the debug build of the 1st iteration worked, so I had a look at the cbp files.

For iteration 1, there is a common set of parameters:

Code

<CodeBlocks_project_file>
    <Project>
        ...
        <Compiler>
            <Add option="`wx-config --cflags`" />
            <Add option="-Wall" />
        </Compiler>
        <Linker>
            <Add option="`wx-config --libs`" />
        </Linker>
        ...
    </Project>
</CodeBlocks_project_file>

whereas for iteration 2 there are separate configs each for debug:

Code

<CodeBlocks_project_file>
    ...
    <Project>
        ...
        <Build>
            <Target title="Debug">
                ...
                <Compiler>
                    <Add option="-g" />
                    <Add option="`wx-config  --version=2.8 --static=no --unicode=yes --debug=yes --cflags`" />
                </Compiler>
                <Linker>
                    <Add option="`wx-config  --version=2.8 --static=no --unicode=yes --debug=yes --libs`" />
                </Linker>
            </Target>
        </Build>
    </Project>
</CodeBlocks_project_file>

and release:

Code

<CodeBlocks_project_file>
    ...
    <Project>
        ...
        <Build>
            <Target title="Release">
                ...
                <Compiler>
                    <Add option="-O2" />
                    <Add option="`wx-config  --version=2.8 --static=no --unicode=yes --debug=no --cflags`" />
                </Compiler>
                <Linker>
                    <Add option="-s" />
                    <Add option="`wx-config  --version=2.8 --static=no --unicode=yes --debug=no --libs`" />
                </Linker>
            </Target>
        </Build>
    </Project>
</CodeBlocks_project_file>

So it turns out that the 1st iteration never actually builds/links against the debug wx libraries. Is this by design, since it seems counter-intuitive?

Cheers and thanks again,
Chris

(Codeblocks SVN 8598 (from https://launchpad.net/~pasgui/+archive/ppa/) on Ubuntu 12.10 x64 with wxGTK 2.8.12.1)

[gd_on]

I've just tried to compile C::B svn 8604 on windows, but it complains for a new cb_release_type environment variable not defined. What are we supposed to put in it ?

gd_on

[MortenMacFly]

I've just tried to compile C::B svn 8604 on windows, but it complains for a new cb_release_type environment variable not defined. What are we supposed to put in it ?

Either -g or -O2.

[kipade]

Its was the first try of CodeBlocks under MS Windows with mingw, but, I found it could not load a UTF-8 encoded text file(including *.c and *.cpp source file)

[killerbot]

after svn up, CB which had the workspace open, asked to reload all the projects ==> let it do it, asked for the global variable var == filled it in, CB continued to reload all the projects ==> crash

[MortenMacFly]

CB continued to reload all the projects ==> crash

Crash log?

[MortenMacFly]

Its was the first try of CodeBlocks under MS Windows with mingw, but, I found it could not load a UTF-8 encoded text file(including *.c and *.cpp source file)

Works for me. Can you send a sample file which does not work? And: Is it really UTF-8?

[SC]

Hi, I just updated to RC2. When using the "Project-> Set programs' argument" menu, modifications in program arguments are lost when clicking on another target. One apparently has to click on "OK" after setting up the argument for a given target, and come back to "Project-> Set programs' argument" to modify the arguments for the next one.
SC

[SC]

2) When using several build targets / environments, it happens that it is not possible to change the compiler flags for a compiler that is not installed on the computer

I cannot reproduce. It works just fine here. Maybe you setup the target so that it is "Windows only"? In that case, just don't do it and you can change flags as you like. (I can.)

Well, if I try to change compiler flags for MSVC8 under linux, I get "the defined compiler cannot be located (ID:msvc8)" even though the build target is not set up to "Windows only".

This is because the Windows-only compilers "do not exist" in Linux builds.  The XML Compiler branch has changed this behavior, but this branch will not be merged until after the release.

Eventually it seems that it was a known issue... Was it worth a RTFM answer?

3) Apparently, when both MSVC2005 and MSVC2008 are installed, C::B does not make the difference

Again: I cannot reproduce. I have two targets: MSVC 2005 and MSVC 2008 and if I change flags for the one target the other is not affected. What exactly are you doing? Steps to reproduce, please?

I will send you a more detailed description of the problem separately.

As promised here is a way to reproduce. (The delay is due to the fact that I did not have a windows computer with bost MSVC8 and MSVC9 accessible). So, I just made a fresh install of the RC2 release.

When using Setting->Compiler, on can select "Microsoft Visual C++ 2005/2008". So apparently it does not make the difference between the two.


If you check out "Search directory", you would find

*compiler
C:\Program Files\Microsoft Visual Studio 8\VC\include
C:\Program Files\Microsoft Visual Studio 9.0\VC\include
C:\Program Files\Microsoft SDKs\Windows\v6.0A\include

*linker
C:\Program Files\Microsoft Visual Studio 8\VC\lib
C:\Program Files\Microsoft Visual Studio 9.0\VC\lib
C:\Program Files\Microsoft SDKs\Windows\v6.0A\lib

*Resource compiler
C:\Program Files\Microsoft Visual Studio 8\VC\include
C:\Program Files\Microsoft Visual Studio 9.0\VC\include
C:\Program Files\Microsoft SDKs\Windows\v6.0A\include

If you check out "Toolchain executables", you would find

*Compiler's installation directory
C:\Program Files\Microsoft Visual Studio 8\VC

*Additional Paths
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE
C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE
C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin

It is mixing directories of MSVC8 and MSVC9. One can correct it by referring to only one of the two versions in the include directories and Compiler's installation directory.

Once again, thank you for this great software.

SC