The 31 December 2023 build (13422) is out.

[killerbot]

We switched to gcc 13.1.0 (on 04 June 2023) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/13.1.0-16.0.5-11.0.0-ucrt-r5/winlibs-x86_64-posix-seh-gcc-13.1.0-mingw-w64ucrt-11.0.0-r5.7z

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(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx324_2D_gcc1310-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls13.1.0.7z


The 31 December 2023 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2023/CB_20231231_rev13422_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

• Clangd_client 1.2.106 23/12/28 Fix completions to not ignore clangd #preprocessor suggestions

Regressions/Confirmed/Annoying/Common bugs:

[Wkerry]

I just updated from a year old nightly to 13422 and I spent an hour trying to figure out what was going wrong with the latest nightly as I get the following alert when I go into the
Envoronment settings:

Code Select Expand

[Window Title]
wxWidgets Debug Alert

[Main Instruction]
A debugging check in this application has failed.

[Content]
C:\wxWidgets-3.2.4\include/wx/strvararg.h(484): assert "(argtype & (wxFormatStringSpecifier<T>::value)) == argtype" failed in wxArgNormalizer(): format specifier doesn't match argument type

[ ] Don't show this dialog again  [Stop] [Continue]

If I disable the Environment variables plugin the alert is not shown. This took me ages to figure out.

More Info:
I did some digging and found a github mirror and one of the following changes could be related to the alert:
    https://github.com/arnholm/codeblocks_sfmirror/commit/2e602238923e652b4aa16f7581ade22e3c69fbaa
    https://github.com/arnholm/codeblocks_sfmirror/commit/c055b1da0af777224207a0601ff22e3a5f2f69b5

[Miguel Gimenez]

Should be fixed in r13423, thank you for reporting.

[nenin]

GDB console, startup:

Code Select Expand

Set variable: PATH=.;C:\mingw64\nixman13_2w32u\bin;C:\mingw64\nixman13_2w32u;C:\mingw64\nixman13_1w32u\bin;C:\mingw64\nixman13_1w32u;C:\mingw64\nixman12_2w32u\bin;C:\mingw64\nixman12_2w32u;C:\Program Files (x86)\Common Files****\WindowsApps;c:\mingw64\nixman13_2w32u\bin
C::B started correct dbg:

Code Select Expand

Starting debugger: C:\mingw64\nixman13_2w32u\bin\gdb.exe
But there are paths to 3 different installation of the MinGW: nixman13_2w32u - actual, nixman13_1w32u - previous, nixman12_2w32u - old one.
Is it OK?

[nenin]

I tried to remove unused GDB profile and got this error.

[Miguel Gimenez]

@nenin, can you list steps to reproduce?. Was the configuration checked in the Debug menu before trying to erase it?.

Running the devel version with gdb should give an useful backtrace.

EDIT: Should be fixed in r13426, but the backtrace would confirm this.

[nenin]

@nenin, can you list steps to reproduce?. Was the configuration checked in the Debug menu before trying to erase it?.
Running the devel version with gdb should give an useful backtrace.

I checked 2 outdated and erratic configs, deleted them and when I pressed OK  I got this error msg.
Apropos, I have very old configs, and I found in one case at work PC that there were broken records, which C::B cannot read properly and as result I observed glitches. It will be nice to have kind of stand-alone verification utility.

[nenin]

Looks like there are solid problems with Mingw GCC.
Such issues, both global and with exact project, jump out very often with different MinGW profiles.

[nenin]

I suppose problematic is this file (see attach), which is located at

Code Select Expand

c:\Users\****\AppData\Roaming\CodeBlocks\share\codeblocks\compilers\options_gcc.xml

[Wkerry]

Could this also cause the issue I have in https://forums.next.codeblocks.org/index.php/topic,25651.msg174598/topicseen.html#msg174598?

[stahta01]

I suppose problematic is this file (see attach), which is located at

Code Select Expand

c:\Users\****\AppData\Roaming\CodeBlocks\share\codeblocks\compilers\options_gcc.xml

With Code::Blocks closed, rename or delete the file above and the file above will stop over riding the normal file of the same name.

Edit: Thank you for your post; I had the same problem. But, I had forgotten where the file that I normally delete was located.

Below is the location I deleted my file from.

Code Select Expand

%APPDATA%\CodeBlocks\share\codeblocks\compilers

Tim S.

[nenin]

With Code::Blocks closed, rename or delete the file above and the file above will stop over riding the normal file of the same name.
Tim S.

I deleted this file, after it C::B starts work OK, but until I try to change compiler in the another one old project . When I open old project with wrong compiler, there is very big probability that this file will be generated again. Only the safe way is to replace compiler manually in text editor. I suppose this is effect, related to compiler autodetection.