1
Development / Re: Change to C++17?
« Last post by Miguel Gimenez on Today at 09:13:56 am »Squirrel warning removed in r14013, thanks christo and LETARTARE.
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
2
Development / Re: Change to C++17?
« Last post by LETARTARE on Today at 12:23:50 am »@christo :Thanks
Errors in Squirrel are removed by the indicated correction. (r14011)
Errors in Squirrel are removed by the indicated correction. (r14011)
3
Nightly builds / Re: The 06 September 2026 build (14003) is out.
« Last post by lp08 on Yesterday at 11:19:05 pm »wxWidgets Debug Allert
A debugging check in this application has failed.
../../src/common/wincmn.cpp(3370): assert "!wxMouseCapture::IsInCaptureStack(this)" failed in captureMouse(): Recapturing the mouse in the same windows?
I'm having a problem reproducing this. Can you give us a few steps to cause the problem?
I opened the project containing my program and two generated log.txt files in Code::Blocks. I executed my program using the MSYS2 terminal. Upon returning to Code::Blocks, I reload the log view, and clicking inside the Code::Blocks interface causes it to crash / throw an error.
4
Development / Re: Change to C++17?
« Last post by killerbot on Yesterday at 08:07:09 pm »I am building the nightlies for a few weeks (?months) with -std=c++23.
I would suggest to step up to 23, and let's avoid extension, so I would suggest not to use 'gnu++xx'.
What do you think ?
I would suggest to step up to 23, and let's avoid extension, so I would suggest not to use 'gnu++xx'.
What do you think ?
5
Development / Re: Change to C++17?
« Last post by stahta01 on Yesterday at 07:50:38 pm »Remember to update the file from "https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx.html" in the "m4" folder.
The link above did not work searching found this link "https://github.com/autoconf-archive/autoconf-archive/blob/master/m4/ax_cxx_compile_stdcxx.m4"
The link above did not work searching found this link "https://github.com/autoconf-archive/autoconf-archive/blob/master/m4/ax_cxx_compile_stdcxx.m4"
6
Development / Re: Change to C++17?
« Last post by christo on Yesterday at 07:17:29 pm »I think plain c++20 should be okay as we do not use any gnu specific extensions.
Regarding squirrel warnings, looks like it is fixed upstream by casting : https://github.com/albertodemichelis/squirrel/commit/6ad6f6427157757c4431907dde0a1e5712a5cf67
Regarding squirrel warnings, looks like it is fixed upstream by casting : https://github.com/albertodemichelis/squirrel/commit/6ad6f6427157757c4431907dde0a1e5712a5cf67
7
Development / Re: Change to C++17?
« Last post by Miguel Gimenez on Yesterday at 07:02:09 pm »Should we use gnu++20 or plain c++20?
8
Development / Re: Change to C++17?
« Last post by Pecan on Yesterday at 06:51:50 pm »I use wx2.3.8 and wx3.3.3 for CodeBlocks (all compiled at c++20) every day.
9
Development / Re: Change to C++17?
« Last post by christo on Yesterday at 06:50:06 pm »Hi Miguel,
I've been using c++20 for a long time without any issues in my custom branch's autotools build on ubuntu. I think we can upgrade to c++20 directly.
For autotools, following change should be sufficient : https://github.com/josephch/codeblocks/commit/c56d5feaf0ce0c5d511263d1fba29e3713af68e2
I've been using c++20 for a long time without any issues in my custom branch's autotools build on ubuntu. I think we can upgrade to c++20 directly.
For autotools, following change should be sufficient : https://github.com/josephch/codeblocks/commit/c56d5feaf0ce0c5d511263d1fba29e3713af68e2
10
Development / Re: Change to C++17?
« Last post by gd_on on Yesterday at 05:49:27 pm »Just to inform you that with my CodeBlocks_Windows.workspace, and setting my global variable cb_build.cpp_std to gnu++20, codeblocks compiles correctly as far as I have tested. Of course, this does not cover all build methods.