The 07 August 2022 build (12859) is out.

[killerbot]

We switched to wx 3.1.7 --> 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_wx317_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 07 August 2022 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2022/CB_20220807_rev12859_win64.7z
  - Linux :
   none

The current SDK version is : 2.19.0

Resolved Fixed:

• wxSmith: Remove duplicated style wxTAB_TRAVERSAL in dialog items.

Regressions/Confirmed/Annoying/Common bugs:

[killerbot]

!!!!!!!!!!!!!!!!!!!! Wx 3.1.7 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[gd_on]

Cool, but the link is still for wx3.1.5

[killerbot]

thanks, link corrected.

[Pecan]

The link to the CB binaries produces the error:

[luisalberto]

 http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2022/CB_20220807_rev12859_win64.7z

Copy this link into the browser instead of _rev12858 it should be _rev12859
and the download will not failed.
 

[AndrewCot]

The Wx3.1.7 DLL's do NOT have the following change back ported and as such I personally would not use 3.1.6/3.1.7 or 3.2.0 until the change is incorporated into it:

   
• https://github.com/wxWidgets/wxWidgets/pull/22651

See the following thread for what issues you will have:

   
• https://forums.next.codeblocks.org/index.php/topic,25031.0.html

Essentially if you use any of the debug dialogs allot you will end up with the dialogs off the screen and you will not be easily get them back onto the screen without modifying the config file to remove the settings. There may be other ways of getting the dialog back on the screen, but I have not investigated.

[Pecan]

@AndrewCot

Thanks, that just saved me a lot of grief.

[killerbot]

the download link is fixed.

[ollydbg]

The Wx3.1.7 DLL's do NOT have the following change back ported and as such I personally would not use 3.1.6/3.1.7 or 3.2.0 until the change is incorporated into it:

   
• https://github.com/wxWidgets/wxWidgets/pull/22651

See the following thread for what issues you will have:

   
• https://forums.next.codeblocks.org/index.php/topic,25031.0.html

Essentially if you use any of the debug dialogs allot you will end up with the dialogs off the screen and you will not be easily get them back onto the screen without modifying the config file to remove the settings. There may be other ways of getting the dialog back on the screen, but I have not investigated.

We can manually apply the fix in our 3.1.7 wx dll.

@killerbot, can you do that?

Another thing I'm thinking is that in some stage/day, we may need "clangd_plugin", because it gives more accurate code completion result than the native code completion plugin. I used this plugin everyday. 

[AndrewCot]

Once the directory where  "clangd_plugin" plugin is to land is sorted I can then start with the back porting of the required changes as I have the changes in my source tree for all of the different build processes (Windows & Linux project  build and Linux and Mac bootstrap/configure/make and the Debian build process).

[killerbot]

clangd_plugin : I would say : contrib plugins location ?  bring it on :-)

[killerbot]

I will apply the fix of wx : https://github.com/wxWidgets/wxWidgets/pull/22651/files
Seems very trivial.

[Miguel Gimenez]

There are two commits, e777a82 and 0e57ed1.

Just copying floatpane.cpp would be easier.

[Pecan]

clangd_plugin : I would say : contrib plugins location ?  bring it on :-)

I prefer adding clangd_client into the contribs also.
We can always move it to core later if needed.
AndrewCot has shown me how to do that.

However, I've been waiting for it to run on all platforms for a whole months without a crash or serious bug before adding it to contribs. So far no cigar.

But it's getting cleaner and (mostly) reliable (thanks a lot to the testers).