User forums > Nightly builds

The 31 December 2023 build (13422) is out.

(1/3) > >>

killerbot:
We switched to gcc 13.1.0 (on 04 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-16.0.5-11.0.0-ucrt-r5/winlibs-x86_64-posix-seh-gcc-13.1.0-mingw-w64ucrt-11.0.0-r5.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_wx324_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 31 December 2023 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2023/CB_20231231_rev13422_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:


* Clangd_client 1.2.106 23/12/28 Fix completions to not ignore clangd #preprocessor suggestions
Regressions/Confirmed/Annoying/Common bugs:

Wkerry:
I just updated from a year old nightly to 13422 and I spent an hour trying to figure out what was going wrong with the latest nightly as I get the following alert when I go into the
Envoronment settings:


--- Code: ---[Window Title]
wxWidgets Debug Alert

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

[Content]
C:\wxWidgets-3.2.4\include/wx/strvararg.h(484): assert "(argtype & (wxFormatStringSpecifier<T>::value)) == argtype" failed in wxArgNormalizer(): format specifier doesn't match argument type

[ ] Don't show this dialog again  [Stop] [Continue]
--- End code ---

If I disable the Environment variables plugin the alert is not shown. This took me ages to figure out.

More Info:
I did some digging and found a github mirror and one of the following changes could be related to the alert:
    https://github.com/arnholm/codeblocks_sfmirror/commit/2e602238923e652b4aa16f7581ade22e3c69fbaa
    https://github.com/arnholm/codeblocks_sfmirror/commit/c055b1da0af777224207a0601ff22e3a5f2f69b5

Miguel Gimenez:
Should be fixed in r13423, thank you for reporting.

nenin:
GDB console, startup:

--- Code: ---Set variable: PATH=.;C:\mingw64\nixman13_2w32u\bin;C:\mingw64\nixman13_2w32u;C:\mingw64\nixman13_1w32u\bin;C:\mingw64\nixman13_1w32u;C:\mingw64\nixman12_2w32u\bin;C:\mingw64\nixman12_2w32u;C:\Program Files (x86)\Common Files****\WindowsApps;c:\mingw64\nixman13_2w32u\bin
--- End code ---

C::B started correct dbg:

--- Code: ---Starting debugger: C:\mingw64\nixman13_2w32u\bin\gdb.exe
--- End code ---
But there are paths to 3 different installation of the MinGW: nixman13_2w32u - actual, nixman13_1w32u - previous, nixman12_2w32u - old one.
Is it OK?

nenin:
I tried to remove unused GDB profile and got this error.

Navigation

[0] Message Index

[#] Next page