Recent Posts

31

Development / Re: Change to C++17?

« Last post by killerbot on September 10, 2026, 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 ?

32

Development / Re: Change to C++17?

« Last post by stahta01 on September 10, 2026, 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"

33

Development / Re: Change to C++17?

« Last post by christo on September 10, 2026, 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

34

Development / Re: Change to C++17?

« Last post by Miguel Gimenez on September 10, 2026, 07:02:09 pm »

Should we use gnu++20 or plain c++20?

35

Development / Re: Change to C++17?

« Last post by Pecan on September 10, 2026, 06:51:50 pm »

I use wx2.3.8 and wx3.3.3 for CodeBlocks (all compiled at c++20) every day.

36

Development / Re: Change to C++17?

« Last post by christo on September 10, 2026, 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

37

Development / Re: Change to C++17?

« Last post by gd_on on September 10, 2026, 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.

38

Development / Re: Change to C++17?

« Last post by Miguel Gimenez on September 10, 2026, 04:38:02 pm »

Have you tried to compile the full version with C++17

I have not tried, developers must agree on the change beforehand. Changing the CBP is easy, the problem may come later from autotools.

Errors in Squirrel can be fixed, but it uses tricky memory accesses that may be a headache.

39

Development / Re: Change to C++17?

« Last post by LETARTARE on September 10, 2026, 03:18:30 pm »

Leap-15.6-64bits, wx-3.2.8;gtk3-u, gc-15.2
'r14003.cbp' ( no 'contrib' )
Here is the compilation log with 'C++17' :

40

Development / Re: Change to C++17?

« Last post by LETARTARE on September 10, 2026, 03:03:09 pm »

Have you tried to compile the full version with C++17 (Win-xx, Linux-xx) ?
If so, what warnings have you obtained ?