The 22 February 2025 build (13620) is out.

[killerbot]

We switched to gcc 14.2.0 (on 09 December 2024) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/14.2.0posix-19.1.1-12.0.0-ucrt-r2/winlibs-x86_64-posix-seh-gcc-14.2.0-mingw-w64ucrt-12.0.0-r2.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_wx326_2D_gcc1420-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls14.2.0.7z


The 22 Februari 2024 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2025/CB_20250222_rev13620_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

• Add options -std=c23 and -std=gnu23 on GCC13 and newer
• BrowseTracker - Rework OnEditorActivate to catch editors loaded via layout
• BrowseTracker - Found/fixed another off-by-one indexing. Optimized array compressing
• SDK: Do not call GetPage() with wxNOT_FOUND (ticket #1513
• UI: Restore project manager tree position after deleting or renaming files (ticket #1514)
• CodeCompletion - Fix clobbered CB global settings changes when closing loaded projects
• Fix compilation with wxWidgets 3.3.0
• Clangd_client Apply Christo patch 1515 cpu usage reduction, thanks Christo

Regressions/Confirmed/Annoying/Common bugs:

[Xaviou]

Hi.

32 bits version for Windows can also be can be downloaded from my website.

Debian Bookworm and Bullseye (32 and 64 bits) can be installed from my repo
The corresponding unsigned deb files can also be downloaded from the website page linked above.

Ubuntu-22.04, 24.04 versions can be installed from my ppa

Regards
Xav'

[Elena]

Sorry I am commenting here since I can't find the original thread re: browse tracker anymore.
I am getting no more slowdowns caused by it, so I could enable it back. It seems definitely fixed. Thanks !

Same for the various hiccups reported while typing (just 80% sure, shall test more).

As for the fix to the list tree position, as I also reported in the relevant ticket there is still a problem when renaming the last file in the list.

Thanks for the update !

[Wkerry]

Finally got around to downloading the 13620 nightly. When I run the codeblocks.exe I get pop up error below, which will cause issues with a bunch of users who are not familiar with the GCC environment as it looks like a C::B issue as looks like it pops up during the startup sequence. The issue is with cc1plus.exe, but

---------------------------
cc1plus.exe - System Error
---------------------------
The code execution cannot proceed because libmpc-3.dll was not found. Reinstalling the program may fix this problem.
---------------------------
OK   
---------------------------

I set the default compiler to no compiler and still got the same issue.

I wonder if my config file has become corrupted/bad.

[stahta01]

Finally got around to downloading the 13620 nightly. When I run the codeblocks.exe I get pop up error below, which will cause issues with a bunch of users who are not familiar with the GCC environment as it looks like a C::B issue as looks like it pops up during the startup sequence. The issue is with cc1plus.exe, but

---------------------------
cc1plus.exe - System Error
---------------------------
The code execution cannot proceed because libmpc-3.dll was not found. Reinstalling the program may fix this problem.
---------------------------
OK   
---------------------------

I set the default compiler to no compiler and still got the same issue.

I wonder if my config file has become corrupted/bad.

That looks to be an GCC toolchain problem to me.

Edit: CB checks for the version of GCC during startup.

Tim S.

[raynebc]

I've found that the "Remove all" function in the Breakpoints window doesn't work unless any of the files containing an existing breakpoint are currently open.