Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on May 27, 2026, 02:48:41 pm

Title: The 27 May 2026 build (13855) is out.
Post by: killerbot on May 27, 2026, 02:48:41 pm
We switched to gcc 15.2.0 (on 09 April 2026) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/15.2.0posix-14.0.0-ucrt-r7/winlibs-x86_64-posix-seh-gcc-15.2.0-mingw-w64ucrt-14.0.0-r7.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 (http://forums.codeblocks.org/index.php/topic,3232.0.html).

A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw33u_gcc_cb_wx332_2D_gcc1520-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls15.2.0.7z


The 27 May 2026 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2026/CB_20260527_rev13855_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 27 May 2026 build (13855) is out.
Post by: killerbot on May 27, 2026, 02:49:41 pm
very important: we switched to wx33.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: killerbot on May 27, 2026, 02:53:22 pm
wx dll was build for the nightlies as follows (using gcc15)

Code
mingw32-make -f makefile.gcc         SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb CXXFLAGS+="-std=c++23" setup_h
mingw32-make -f makefile.gcc -j 26 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb CXXFLAGS+="-std=c++23"
==> -std=c++23

and CB was also build like that (CB nightlies are build by using CB) by having the global variable "cb_cpp_std" the value "-std=c++23".

Title: Re: The 27 May 2026 build (13855) is out.
Post by: killerbot on May 27, 2026, 02:54:03 pm
next up in the near future will be a switch to gcc16 (and maybe -std=c++26) ...
Title: Re: The 27 May 2026 build (13855) is out.
Post by: Xaviou on May 27, 2026, 10:46:23 pm
Hi.

32 bits version for Windows (and also 64 bits version) can be downloaded from my website (https://wxstuff.xaviou.fr/article/codeblocks-nightly-builds.html).
I made both a wxWidgets-3.2.10 and wxWidgets-3.3.2 linked versions

Debian Trixie (64 bits) and Bookworm (32 and 64 bits) can be installed from my repo (https://wxstuff.xaviou.fr/article/debian-repository.html)
The corresponding unsigned deb files can also be downloaded from the website page linked above.

Ubuntu-22.04, 24.10 and 26.04 versions can be installed from my ppa (https://launchpad.net/~x-psoud/+archive/ubuntu/cbnb) (they are now available for both amd64 and arm64 architectures).

Regards
Xav'
Title: Re: The 27 May 2026 build (13855) is out.
Post by: luisalberto on May 27, 2026, 11:09:19 pm
I Check this nightly and When I close codeblocks.exe this debug alert messageBox appear. Ctrl + C to copy the messgeBox

[Window Title]
wxWidgets Debug Alert

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

[Content]
../../src/aui/auibook.cpp(2756): assert "page_idx < m_tabs.GetPageCount()" failed in GetPage().

[ ] Don't show this dialog again  [Stop] [Continue]
[Window Title]
wxWidgets Debug Alert

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

[Content]
../../src/aui/auibook.cpp(2856): assert "Assert failure" failed in FindTab(): Window unexpectedly not found in any tab control

[ ] Don't show this dialog again  [Stop] [Continue]
Title: Re: The 27 May 2026 build (13855) is out.
Post by: ThierryD on May 28, 2026, 12:10:26 pm
Hi,

Just "critical detect" with Bit Defender AV during download: Gen:Suspicious.Cloud.1.bOX@aWYtNEb. 

Regards.

TDE
Title: Re: The 27 May 2026 build (13855) is out.
Post by: Pecan on May 29, 2026, 06:45:25 am
I Check this nightly and When I close codeblocks.exe this debug alert messageBox appear. Ctrl + C to copy the messgeBox

[Window Title]
wxWidgets Debug Alert

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

[Content]
../../src/aui/auibook.cpp(2756): assert "page_idx < m_tabs.GetPageCount()" failed in GetPage().

[ ] Don't show this dialog again  [Stop] [Continue]
[Window Title]
wxWidgets Debug Alert

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

[Content]
../../src/aui/auibook.cpp(2856): assert "Assert failure" failed in FindTab(): Window unexpectedly not found in any tab control

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

I've found that deleting the .conf file just one time solved this for me.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: eckard_klotz on May 29, 2026, 12:27:56 pm
Hello All

If got a detection with Norton 360 while downloading the file "CB_20260527_rev13855_win64.7z" also:

I don't get this detection if I download the files provided by Xaviou.
But after running a system-test on my laptop the same file "cb_console_runner.exe" was detected in the decompressed nightly from 9th of April 2026 (revision 13831).

I have reported this as a wrong detection and I've got the response that the case will be checked and I should try it in 24 hours again.

Best regards,
                      Eckard.

Title: Re: The 27 May 2026 build (13855) is out.
Post by: MaxGaspa on May 29, 2026, 01:37:48 pm
I've found that deleting the .conf file just one time solved this for me.

Yes. But I customized my default.conf in the last 5 years. To re-build manually all the cutomizations and settings is boring and time consuming. I do hope a workaround exists. Is there any other possible modification of the default.conf to fix the issue?

Another point. My understanding was that with wx332 the dak mode is available. But I don't find any setting to enable it, using both my and new defautl.conf. Is the dark mode available is this nightly?

Thx

Max
Title: Re: The 27 May 2026 build (13855) is out.
Post by: luisalberto on May 29, 2026, 11:23:19 pm
You can change the colors using Environment Settings, Select Colours Image or Icon, Below is a comBoBox that say select application appearance if(supported by platform) and you can change the combobox to 3 options system default, Light , Dark theme.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: Pecan on May 29, 2026, 11:53:42 pm
I've found that deleting the .conf file just one time solved this for me.

Yes. But I customized my default.conf in the last 5 years. To re-build manually all the cutomizations and settings is boring and time consuming. I do hope a workaround exists. Is there any other possible modification of the default.conf to fix the issue?

Another point. My understanding was that with wx332 the dak mode is available. But I don't find any setting to enable it, using both my and new defautl.conf. Is the dark mode available is this nightly?

Thx

Max

Try deleting all the .layout files to see if that fixes the problem.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: ThierryD on May 31, 2026, 03:25:28 pm
Thanks Eckhart,

Today, I retry to download and diagnostic is same but Trojan detected not (???) (in file join).

I will try download nightly CB on Linux first (on my laptop with double boot), I will try to decompress always on Linux (partition NTFS with access "write"), and after reboot on W11 2H2 to see result.

Regards.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: MaxGaspa on June 02, 2026, 10:26:59 pm
You can change the colors using Environment Settings, Select Colours Image or Icon, Below is a comBoBox that say select application appearance if(supported by platform) and you can change the combobox to 3 options system default, Light , Dark theme.

There is no Environment Settings, Select Colours Image or Icon. I'm using Windows 11 25H2. So dark mode is not supported in Windows 11?
Title: Re: The 27 May 2026 build (13855) is out.
Post by: MaxGaspa on June 02, 2026, 10:32:54 pm
Try deleting all the .layout files to see if that fixes the problem.

No. It doesn't work. So the only solution is to re-customize everything. Very boring and time consuming. Am I the only one with this issue?
Title: Re: The 27 May 2026 build (13855) is out.
Post by: ThierryD on June 03, 2026, 04:35:24 pm
Today, I try to download this last nightly of CB into WSL2 (Ubuntu 24.04) using Firefox browser (just my choice ...  ;D  )

BitDefender AV don't control this 7z archive (YES !), by default stored on "$HOME/Downloads".

Into terminal Ubuntu 24.04, I use command "7z" to extract directly to "/mnt/c/CodeBlocks", ... and BD AV detect like previous downloads an malware, and, like Eckart, link to file "CB_soncole_runner.exe" just decompressed ...

I force BD AV to restore this specific file. 

After that, I run CB (after decompress also two dependencies files with MinGW64 and WX DLL), and result is OK.

I don't know why, CB has been very long time to start ... but (be patient) ..., after I can use last nightly of CB normally.

Story is closed !

Thank's.




 

Title: Re: The 27 May 2026 build (13855) is out.
Post by: MaxGaspa on June 04, 2026, 10:44:04 am
I lookfor a setings to get the dark mode using this nightly and Windows 11 25H2. It seems there is no such an option. So can you confirm that dark mode is not supported in Windows 11? Is it possible to enable the dark mode in Windows11? Is a long waited feature....
Title: Re: The 27 May 2026 build (13855) is out.
Post by: gd_on on June 04, 2026, 11:30:15 am
You can use C:B in darkmode. At least 2 ways to obtain this :
Code
REM To force darkmode (if 0 standard color mode, if 1 follow system mode)
set WX_MSW_DARK_MODE=2
codeblocks.exe
Then you can adjust different colors.
In this example, this codeblocks_DarkMode.cmd file is placed where codeblocks.exe is installed.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: MaxGaspa on June 04, 2026, 11:47:37 am
set WX_MSW_DARK_MODE=2

Thanks...I wasn't aware of the environment variable WX_MSW_DARK_MODE. Now I set this environment variable and I'm able to switch between the two modes quickly.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: MaxGaspa on June 04, 2026, 11:54:22 am
[Main Instruction]
A debugging check in this application has failed.
I've found that deleting the .conf file just one time solved this for me.

Pecan, trying to re-customize my default.conf I think I found the root cause of the issue and so a quick way to fix it. The root cause of the debugging checks is a specific setting

Settings->Environment Settings->Notebooks Appearance->Tab Style

If you set the tab style to Firefox2 or Microsoft Visual Studio 7.1 the debugging checks are raised

Uisng default or Simple Tabs no debugging checks are raised.

So to me is enough to change my old settings from Firefox 2 to default to get a working default.conf (my old one). I hope this helps to understand how to fix the issue.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: luisalberto on June 04, 2026, 04:07:09 pm
Goto to Settings -> Environments Select Colours and over the OK and Cancel Buttons You will see the combo Box to change the theme. I am using Windows 11 25 H2. See the attach Image file. I dont like the dark mode and I use Light mode in Codeblocks.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: gd_on on June 04, 2026, 04:39:00 pm
Effectively, I forgot to mention this as a third solution, introduced quite recently.
Nevertheless, the 2nd solution may be applied to many wxwidgets softwares where darkmode is not explicitely implemented. 
Title: Re: The 27 May 2026 build (13855) is out.
Post by: 20k on June 17, 2026, 10:27:58 pm
[Main Instruction]
A debugging check in this application has failed.
I've found that deleting the .conf file just one time solved this for me.

Pecan, trying to re-customize my default.conf I think I found the root cause of the issue and so a quick way to fix it. The root cause of the debugging checks is a specific setting

Settings->Environment Settings->Notebooks Appearance->Tab Style

If you set the tab style to Firefox2 or Microsoft Visual Studio 7.1 the debugging checks are raised

Uisng default or Simple Tabs no debugging checks are raised.

So to me is enough to change my old settings from Firefox 2 to default to get a working default.conf (my old one). I hope this helps to understand how to fix the issue.

This didn't work for me (I'm experiencing the same problem), as my tabs were set to default already
Title: Re: The 27 May 2026 build (13855) is out.
Post by: eckard_klotz on July 18, 2026, 12:35:10 pm
Hello Developers.

Unfortunately the folding margin is located next to the text inside the editor and thus, it happens very easily that you force a folding even you just want click at the first line position, what is very annoying.

While reviewing the current margin configuration in cbEditor.cpp, I noticed that Code::Blocks defines its own margin IDs:

Code
#define C_LINE_MARGIN      0
#define C_MARKER_MARGIN    1
#define C_CHANGEBAR_MARGIN 2
#define C_FOLDING_MARGIN   3


As far as I understand it, Scintilla (and wxScintilla) always render margins strictly in ascending ID order.
Because of this, the folding margin (ID 3) appears directly next to the text area in the editor. This placement makes it easy to accidentally trigger fold/unfold actions when clicking near column 1, especially on high‑resolution displays.

Other Scintilla‑based editors (SciTE, Geany, Notepad++) avoid this issue by placing the folding margin immediately to the right of the line‑number margin. This provides a natural buffer zone and significantly reduces accidental folding.

In Code::Blocks, the folding margin is configured here:

Code
control->SetMarginType(C_FOLDING_MARGIN, wxSCI_MARGIN_SYMBOL);
control->SetMarginWidth(C_FOLDING_MARGIN, foldingMarginBaseWidth);
control->SetMarginMask(C_FOLDING_MARGIN, ...);
control->SetMarginSensitive(C_FOLDING_MARGIN, 1);


Since all margin‑related logic consistently seems to use the symbolic constants (C_FOLDING_MARGIN, C_MARKER_MARGIN, etc.), adjusting the margin order is limited to changing the four #define values. No other code changes should be required, and no plugins or configuration files are affected.

Suggested improvement: 
Reassign the folding margin to a lower ID (e.g., 1), so the margin order becomes:

Line numbers → Folding → Marker → Changebar → Text


This can simply be changed while the definition of the preprocessor constants like this:

Code
#define C_LINE_MARGIN      0
#define C_FOLDING_MARGIN   1
#define C_MARKER_MARGIN    2
#define C_CHANGEBAR_MARGIN 3


I think this small, isolated change would align Code::Blocks with common Scintilla practice and improve usability without introducing new settings or breaking existing functionality.


Please take a look to this and thank you in advance.

Best regards,
                   Eckard Klotz.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: Miguel Gimenez on July 19, 2026, 08:55:51 pm
I have increased margin size from 16 to 22 and made it dependent on scale factor, see r13915 (https://sourceforge.net/p/codeblocks/code/13915/).

EDIT: Clicking in the gap between the fold box and the text editor still fires folding  :o , so this change only fixes box size in HiDPI. Relating margin order, I prefer it as is.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: eckard_klotz on July 20, 2026, 12:52:33 pm
Hello Miguel Gimenez.

Quote
... Relating margin order, I prefer it as is. ...


If you prefer the current margin order but your users not the alternative will be to make the margin order configurable.
But I fear this will mean much more effort for you.
Thus, I just ask you to solve the folding issue and changing the margin order is a simple way to fix the issue without disabling the folding completely.     

Best regards,
                   Eckard Klotz.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: cacb on September 01, 2026, 11:56:04 am
Hello,  I have been reading this thread to see if I am able to enable dark mode in C::B
I am running Windows 10 (dark mode) and C::B nightly build 13961. I tried the following


set WX_MSW_DARK_MODE=1
codeblocks.exe


I am able to get the C::B application in dark mode, but the code editor is still in light mode and I don't really understand why, see attached screenshot. Is this due do some old .conf file I am using or is there an easy way to get the editor window to appear in dark mode without having to redefine every detail?

Related question: I am also running C::B on Linux Kubuntu. Is there a way to enable dark mode there?

EDIT: On Kubuntu 24.04 KDE and using C::B 13924 I was able to achieve a similar dark mode effect as on Windows 10, but still the editor is in light mode:

export GTK_THEME=Adwaita:dark
codeblocks&

Title: Re: The 27 May 2026 build (13855) is out.
Post by: Miguel Gimenez on September 01, 2026, 12:05:09 pm
You do not need to set variables, there is a setting in Environment -> Colours to enable dark mode. This should work also on Kubuntu.

The editor window (cbStyledTextCtrl) is based in old wxWidgets code and does not currently support dark mode. Other parts of the UI in dark mode have been fixed after r13961, see r13969 to r13972, r13975 and r13976.

Some wxWidgets items still do not work correctly in dark mode, wxMessageDialog for example.
Title: Re: The 27 May 2026 build (13855) is out.
Post by: cacb on September 01, 2026, 12:13:31 pm
Thank you for the answer. On Kubuntu, the option under Environment -> Colours, i.e. "Select application appearance (if supported by platform)" is disabled, so I am not able to select anything. It says "System Default" only.

Thank you for the clarification of the missing dark mode in the editor window. That is a pity, but at least it is clear.

EDIT: Given no support for dark mode in the editor, I have been looking for a way to change the main background colour of the editor window to something other than white. This is not a perfect solution, but it may give some eye relief: Settings -> Editor -> Syntax highlighting
Then select something other than pure white as background, for example light blue (H,S,L) = (140,240,200).

EDIT2: On closer inspection, it is possible to achieve a decent dark mode in the editor using Settings -> Editor -> Syntax highlighting  and creating a new "Colour theme" called e.g. DarkMode and change all the relevant colours including foreground/background and C++ language related colours, I did this and copied the relevant section of default.conf from Windows to Linux so now I have a working dark mode of both the C::B IDE and the code editor. At least it seems good enough to try to use it. This means to switch from default to dark mode or vice versa you have to do 2 things

 Settings -> Environment -> Colours    "Select application appearance (if supported by platform)"  (or use environment variable as needed)
 Settings -> Editor -> Syntax highlighting    Select the relevant user defined colour theme.