The 09July 2022 build (12847) is out.

[killerbot]

We switched to wx 3.1.5 --> download the new wx dll's see link below

If you tested the 22 january nightly you may find your compiler executable has changed from gcc.exe to mingw32-gcc.exe and g++.exe to mingw32-g++.exe. Please correct this, you won't be asked again.

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


The 09 July 2022 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2022/CB_20220709_rev12847_win64.7z
  - Linux :
   none

The current SDK version is : 2.19.0

Resolved Fixed:

• Fix compilation of wx3.1.6 and later with Clang (thanks AndrewCot).
• compiler: Update AVR gcc compiler flags. Add missing uC and add some comments for better readability.
• ccmanager - ccmanager ignores completion requests when its length is the same as the previously request.

Regressions/Confirmed/Annoying/Common bugs:

[Neo]

wxWidgets 3.2.0 Released, any plan to use this new release?

[AndrewCot]

There are a number of posts about wxWidgets 3.2.0 RC's and final versions that you should be reading about where devs are up to with wx3.2.0, but at this exact point in time it is too new to update the nightly IMHO as the most of the C::B devs are in the process of updating to it for their local builds or have just done it in the last few days/weeks.

If you want to use it ASAP then I would recommend creating a new post in the help forum if you do not know how to build wxWidgets 3.2.0 and C::B. If you do know how to build wxWidegts and CB then there should be nothing stopping you once you make the appropriate build changes from wx3.1.x to wx3.2.0.

[killerbot]

I think I will first step-up to wx 3.1.7, and then we try 3.2.0 ....