Recent Posts

71

Nightly builds / The 16 August 2025 build (13710) is out.

« Last post by killerbot on August 16, 2025, 04:47:15 pm »

We switched to gcc 15.1.0 (on 23 May 2025) --> 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.1.0posix-12.0.0-ucrt-r1/winlibs-x86_64-posix-seh-gcc-15.1.0-mingw-w64ucrt-12.0.0-r1.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_wx328_2D_gcc1510-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls15.1.0.7z


The 16 August 2025 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2025/CB_20250816_rev13710_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

• incremental search plugin: fixed resource ZIP command in wx33 project file
• incremental search plugin: fixed resource ZIP command in wx32 project file
• Fix crash on start with wx3.3.1 due to an index out of bound
• Really fix font size in disassembly window (ticket #1529).
• ToolsPlus: Really fix font size in HiDPI (ticket #1529).
• applied patch #1543 by Christo: clangd_client: some stability fixes
• applied patch #1542 by Christo: clangd_client : if filterText not present in completion response, use label instead

Regressions/Confirmed/Annoying/Common bugs:

72

Contributions to C::B / Re: macOS + Fortran contributions

« Last post by Miguel Gimenez on August 16, 2025, 04:06:12 pm »

Fortran project is a contributed plugin with its own developer and site. Some of us have write access to the repository, but we usually only modify parts not related to the fortran core (p.e. HiDPI changes).

73

Contributions to C::B / Re: macOS + Fortran contributions

« Last post by perazz on August 16, 2025, 03:24:00 pm »

Sounds good, thank you.

So I will open a ticket with the patch file attached.

for Fortran plugin updates, should I also send ticket to the master C::B repository?

74

Contributions to C::B / Re: macOS + Fortran contributions

« Last post by Miguel Gimenez on August 16, 2025, 01:10:26 pm »

Any contribution is welcome, specially those from Mac developers.

The best method for contributing, at least for the initial ones, is posting Subversion patches in the ticket page. Posting in the forum is also valid, but once a post disappears from the main window it will probably be forgotten.

75

Development / Re: Error when compiling parser.cpp in svn 13708

« Last post by Miguel Gimenez on August 16, 2025, 12:58:33 pm »

Fixed in r13710.

76

Development / Re: Error when compiling parser.cpp in svn 13708

« Last post by christo on August 16, 2025, 12:20:33 pm »

In the patch I provided in https://sourceforge.net/p/codeblocks/code/13708 it was

Code

size_t remainingToParse = pParser ? pParser->GetFilesRemainingToParse() : 0;

I think we should change nullptr back to 0 as above.

77

Development / Error when compiling parser.cpp in svn 13708

« Last post by gd_on on August 16, 2025, 11:25:47 am »

C:\Users\Gerard\Documents\CodeBlocks_SVN\CodeBlocks_src\src\plugins\contrib\clangd_client\src\codecompletion\parser\parser.cpp|1662|error: operands to '?:' have different types 'size_t' {aka 'long long unsigned int'} and 'std::nullptr_t'|

This error is obtained with MingW64 / Msys2 g++ 15.2 on Windows. Adding an explicit cast to site_t before nullptr corrects the compilation error. But is it the correct solution ?

78

Contributions to C::B / macOS + Fortran contributions

« Last post by perazz on August 15, 2025, 06:59:10 pm »

Hi all,

after long time I've eventually achieved a setup that lets me contribute to CodeBlocks (it's a great code!) and use it profitably on macOS.

To build it successfully I have generated some .cbp macOS project files, and fixes to actually run it (some wxTimer issues would cause segfaults when compiled with clang++).
And, I would like to contribute some advances to the Fortran plugin.

So my question is, how does the SourceForge workflow work? I currenlty use a svn->git repository but I can submit patches either here on the Forum, or on SourceForge directly.

Thank you in advance and let's please discuss what you think is the best approach.

Best,
Federico

79

General (but related to Code::Blocks) / Re: wxWidgets 3.3.1 can only be used in the ucrt platform, not the mingw64 platform?

« Last post by MehdiChinoune on August 14, 2025, 06:06:01 pm »

I did it in purpose with many new packages, so people start migrating to UCRT64.

80

General (but related to Code::Blocks) / Re: wxWidgets 3.3.1 can only be used in the ucrt platform, not the mingw64 platform?

« Last post by ollydbg on August 14, 2025, 06:35:29 am »

The MSys2 team no longer considers MINGW64 an fully maintained environment. Therefore, they are no longer creating new packages that support it.

Tim S.

Thanks for the reply. This is really a bad news for me. If I would like to use wx3.3.1 prebuild library under msys2, I have to switch all my platform from msvcrt(mingw64) to ucrt(ucrt64).