The 03 June 2023 build (13304) is out.

[killerbot]

We switched to gcc 13.1.0 (on 03 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-11.0.0-ucrt-r3/winlibs-x86_64-mcf-seh-gcc-13.1.0-mingw-w64ucrt-11.0.0-r3.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_wx3221_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 03 June 2023 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2023/CB_20230603_rev13304_win64.7z
  - Linux :
   none

The current SDK version is : 2.24.0

Resolved Fixed:

• Check tree item validity before using it, as it is done just below
• ProjectsImporter: Fix import of MSVC++ 6 workspaces (ticket #1392)
• Clangd_client 1.2.70 23/05/11 Translate the the project folder name to UTF-8 for clangd initialization (Thanks Trigger)
• wxSmith: Add setting for using Bind() instead of Connect(), disabled by default.
• CompilerGCC: Disable Run button if the executable does not exist (ticket #1395, thanks LETARTARE)
• add and update XML compile specs
• allow a new node type "macros" in XML compilers that can be used for search paths like $(CODEBLOCKS)/MinGW
• added wxSmithDemo project files for wx31 and wx32
• updated ContribPlugins workspace (fixed wrong dependency)
• modernise/update crash handler dll (exchndl) from v0.9.9 to v0.9.11 (Windows only change)
• added forgotten compiler options file for mingw32

Regressions/Confirmed/Annoying/Common bugs:

[killerbot]

in case you use Win7/8, realise that OS is obsolete, but you should be able to use the builds based upon the UCRT ( Universal C Run Time) :
https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c

[killerbot]

questions : this one is based upon : MCF threads, the compiler builders also provide a 'posix threads' version, which one would be best suited to use ?

[Khram]

First start

[luisalberto]

Hi, The program do no start unless you provide the library libmfcgthread-1.dll which i downloaded from the bin
directory of the winlibs compiler version 13.1. Normally I use the posix version of the compiler right now latest release version 4. Im using windows 11. I downloaded all three zips files and extracted the libmfcthread-1.dll from the zip file of the winlibs mingw64.

[killerbot]

when posting the nightly I was already kind of inspecting this, the content of the zip of those dlls, was based on the content of the previous system. Which was posix, so the current one is that mcf, so indeed makes sense that one should be in the zip now instead of the posix one.

This also seems to indicate which better stick to posix ..... ?

I think last time by mistake I took the mcf (or mayb the posix was not there at that time ... ??)

Any ideas, suggestions, ...

[killerbot]

http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls13.1.0.7z  has been reuploaded, containg 4 dll's now (including libmcfgthread-1.dll)

[Khram]

http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls13.1.0.7z  has been reuploaded, containg 4 dll's now (including libmcfgthread-1.dll)

Ok! Very thanks.

[tomay3000]

Thank you for the update.
I think MCF threading model is still in test mode though it is faster than the POSIX one, and we should not use it in production apps to end users because it can blow up in our faces at any moment.

Question: Why have chosen Winlibs over Mingw-Builds https://github.com/niXman/mingw-builds-binaries/releases?

Mingw-Builds are still updated as you can see by niXman and I am trying to keep SJLJ exceptions model for x86 updated as well, and that is for compatibility reasons only, and you can get them here: https://github.com/tomay3000/mingw-builds-binaries/releases

[killerbot]

great, good information coming in :-)

I will make a new nightly this week, switching back to posix.

Why winlibs, well the previous releases/nightlies were using : https://sourceforge.net/projects/mingw-w64/files/. ===> Which seems dead.
For some years I wanted to switch back to TDM (gcc 10), but problems were reported in the forum, so I never tried.

So I did some minimal googling and ended up at winlibs, and gave it a try, and it seems to work ok. No build issues at all, in the process.

Looking at it again : https://www.mingw-w64.org/downloads/#mingw-builds
Winlibs is indeed the second entry, and the ones you mention is actually the first entry.

I don't remember, I think I might have come across these 2, my experiments are like over 1 month old, and the fact winlibs had gcc13 most probably influenced my selection.

To be honest, I don't know the differences between the 2 sets. I would suggest that as winlibs has some explanation on that page , that would also be welcome for your set.

And I think already in the past a google search also already had shown me winlibs, since on a test machine it was on the bookmarks toolbar of firefox ;-)

[Khram]

Still, it's better and easier to use C++ assembly from http://www.equation.com/servlet/equation.cmd?fa=programminglog   -->>  http://www.equation.com/servlet/equation.cmd?fa=fortran  +++  ftp://ftp.equation.com/gcc/

[Neo]

Windows Security reports *severe* threat in CbLauncher.exe! Is it a false positive?

[MortenMacFly]

I will make a new nightly this week, switching back to posix.

Yes please, I would prefer that, too and Brecht Sanders has just released a version (Release 4) that works just fine for me. Indeed way better than the MFC one (which has trouble with quite some libraries I regularly use).

[MortenMacFly]

Question: Why have chosen Winlibs over Mingw-Builds https://github.com/niXman/mingw-builds-binaries/releases?

Just my 2 cents here: The WinLibs version comes with most common libs included that is very helpful if you start programming. I assume that we will avoid quite some programming questions if we ship these just with the compiler. Code::Blocks is intensively used in schools, universities or alike so this is probably a good thing to do.

But of course: Only one setup will include the compiler which is intended for beginners and "lazy" professionals. Professionals can and probably should select the compiler upon their needs, install themselves and setup as desired.

[tomay3000]

What I wanted to say is:

• Just avoid MCF for now as it is not ready yet and may cause problems in the future and just stick to POSIX even though MCF is mentioned by MinGW-w64 website itself.
• Mingw-Builds by niXman https://github.com/niXman/mingw-builds-binaries/releases is the official continuation (updated by MinGW-w64 website itself) to the previous dead one https://sourceforge.net/projects/mingw-w64/files.
• Winlibs is just fine if you chose the right Toolchain.
• My personal favorite is Mingw-Builds by niXman https://github.com/niXman/mingw-builds-binaries/releases as he provide the source code as well https://github.com/niXman/mingw-builds that I forked from to bring SJLJ for x86 to life again.