51
Using Code::Blocks / Re: [Solved]How to set different debugger for each build target?
« Last post by Miguel Gimenez on September 17, 2026, 01:30:52 pm »Spam reported to moderator.
News:
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
Recent Posts
52
Development / Re: Change to C++17?
« Last post by christo on September 17, 2026, 06:10:53 am »My current development environment (MinGW8.1) only supports upto C++2a, I can change C::B to C++20 or C++23 but then I will be out of the game for a while...I think c++17 should be fine for now
53
Using Code::Blocks / Re: [Solved]How to set different debugger for each build target?
« Last post by SmithJoe on September 16, 2026, 03:32:47 pm »Hi, everyone.
It seems that debugging a 32bit program with 64bit GDB doesn't work on Windows 7, so I create two debugger settings: one for 32bit, the other for 64bit, and I want to set different debugger for each build target(e.g. 32bit target use 32bit GDB, 64bit target use 64bit GDB), but I can't find any settings for this, I know how to change active debugger manually, but how to do this auto when I switch build targets.
I use CodeBlocks DEBUGGER BRANCH rev7790.
Sorry for my bad english. Thanks!
Interesting issue. It would be useful if Code::Blocks could automatically switch the debugger based on the selected build target.
54
Development / Re: Change to C++17?
« Last post by Miguel Gimenez on September 16, 2026, 02:18:20 pm »My current development environment (MinGW8.1) only supports upto C++2a, I can change C::B to C++20 or C++23 but then I will be out of the game for a while...
55
Development / Re: It's year 2026, so I think some text like: 2024-2025 can be updated to 2026
« Last post by Miguel Gimenez on September 15, 2026, 11:17:09 am »Prostitution spam reported to moderator.
56
Nightly builds / Re: The 06 September 2026 build (14003) is out.
« Last post by Pecan on September 12, 2026, 07:13:31 pm »When working on builds for Fedora (https://copr.fedorainfracloud.org/coprs/sharkcz/danny/build/10959184/, details are in the builder-live.log files), I have noticed that libtool version 2.6.2 present in Rawhide fails the build of the codesnippets plugin after the tinyxml LIBADD was removed from its Makefile.am in revision 13996. System tinyxml library is used in the builds. I have confirmed that with libtool downgraded to 2.5.4 the build runs OK. AFAICT other plugins still use the LIBADD mechanism. Likely some change in libtool is causing this ...
Thanks for the report.
Fixed svn r14017
57
General (but related to Code::Blocks) / Re: Faild to build C::B with github action with latest wxWidgets 3.3.3
« Last post by Pecan on September 12, 2026, 07:10:09 pm »Hi Pecan,
I think some lines in Makefile.am were deleted accidently in revision 13996, restoring that should fix the issue.
https://sourceforge.net/p/codeblocks/code/13996/tree//trunk/src/plugins/contrib/codesnippets/Makefile.am?diff=51421f1dc431436b6eb31d56:13995
Thanks. I have no idea how that happened.
Fixed svn 14017
58
Using Code::Blocks / Perfomance question: CodeBlocks "normal" RAM usage and file closing delay
« Last post by CH4Code on September 12, 2026, 01:01:57 pm »Hi,
I have been using CodeBlocks for hobby projects for a while now and upgraded from the 2020 Version to the 25.03 Version a while back.
However I have noticed some very slow reaction times in the 25.03 version and investigated the issue, which I did not have with C::B 2020.
Especially when I close files, it freezes the application for about 10 seconds, which doesn't make any sense to me.
I also noticed that C:B consumes 4GB of RAM by just starting it, pushing my memory to above 90% used. Is this normal? I'm sorry to compare but Visual Studio with a loaded complex project only consumes ~500MB of RAM.
Also while closing my project the RAM usage suddenly increases by 1GB and never quite goes down again. How does that make any sense?
Finally, I have to reload my project quite often because I use cmake to re-generate the project file whenever I add or change resources etc. and that also takes about 30-45 seconds, which feels a bit painful.
I'm on windows 11 (8GB RAM), using msys2, mingw64, cmake, ninja, with CodeBlocks.
I don't remember having an issue with CB 2020 before (closing files being slow).
1) Can I do anything to reduce the RAM usage of CB or 2) the file closing issue? 3) Is this amount of memory usage expected?
I already reinstalled CodeBlocks and got rid of an unrelated "lib_finder.dll not found" error, thanks to forum posts, maybe you can help me out here, too?
Thank you.
I have been using CodeBlocks for hobby projects for a while now and upgraded from the 2020 Version to the 25.03 Version a while back.
However I have noticed some very slow reaction times in the 25.03 version and investigated the issue, which I did not have with C::B 2020.
Especially when I close files, it freezes the application for about 10 seconds, which doesn't make any sense to me.
I also noticed that C:B consumes 4GB of RAM by just starting it, pushing my memory to above 90% used. Is this normal? I'm sorry to compare but Visual Studio with a loaded complex project only consumes ~500MB of RAM.
Also while closing my project the RAM usage suddenly increases by 1GB and never quite goes down again. How does that make any sense?
Finally, I have to reload my project quite often because I use cmake to re-generate the project file whenever I add or change resources etc. and that also takes about 30-45 seconds, which feels a bit painful.
I'm on windows 11 (8GB RAM), using msys2, mingw64, cmake, ninja, with CodeBlocks.
I don't remember having an issue with CB 2020 before (closing files being slow).
1) Can I do anything to reduce the RAM usage of CB or 2) the file closing issue? 3) Is this amount of memory usage expected?
I already reinstalled CodeBlocks and got rid of an unrelated "lib_finder.dll not found" error, thanks to forum posts, maybe you can help me out here, too?
Thank you.
59
Development / Re: svn14014 regression: cb compile syntax error
« Last post by Miguel Gimenez on September 12, 2026, 10:34:39 am »Fixed, thank you. I wrote this using wx3.0, so it went unnoticed.
60
General (but related to Code::Blocks) / Re: Faild to build C::B with github action with latest wxWidgets 3.3.3
« Last post by christo on September 12, 2026, 05:38:41 am »Hi Pecan,
I think some lines in Makefile.am were deleted accidently in revision 13996, restoring that should fix the issue.
https://sourceforge.net/p/codeblocks/code/13996/tree//trunk/src/plugins/contrib/codesnippets/Makefile.am?diff=51421f1dc431436b6eb31d56:13995
I think some lines in Makefile.am were deleted accidently in revision 13996, restoring that should fix the issue.
https://sourceforge.net/p/codeblocks/code/13996/tree//trunk/src/plugins/contrib/codesnippets/Makefile.am?diff=51421f1dc431436b6eb31d56:13995