Recent Posts

31

Help / Re: Used .deb files to install Codeblocks

« Last post by Atudeas on April 24, 2026, 09:17:07 am »

Hi there,

I've installed Cobeblocks from de 25.03 .dev files from the Codeblocks site block blast. After that I installed the .deb files for WxSmith. But in both cases I get a build 13046 wich is from 2022-11-18. How can I upgrade to 25.03? Usually I use the install app on Kubuntu, but that one also had an older version.

I'm not a console wizzard.

You can try upgrading Code::Blocks to 25.03 using a Debian file. If you are using Ubuntu 24.04 / Linux Mint 22, download the file codeblocks25.03amd64debian12.tar.xz. If you are using Ubuntu 22.04 / Linux Mint 21, download the file codeblocks25.03amd64debian11.tar.xz.

32

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by ilyacolton on April 24, 2026, 05:28:24 am »

Nah, there's no "universal" script or program for that, dude. Project files are usually super specific to each IDE/tool; typically, we use cross-platform build systems like CMake or framework-specific tools (like Qt) to manage projects between Linux and Windows.
fnaf

33

Help / Re: c++23

« Last post by stahta01 on April 23, 2026, 09:11:19 pm »

my advice: don't use pcm.


I have several projects using C++23 in CB, even C++26.

PCM as in Precompiled Modules in C++26 (the upcoming C++ standard)

34

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by Miguel Gimenez on April 23, 2026, 09:05:57 am »

Delayed profile spammer predictbong reported to moderator.

35

Help / Re: c++23

« Last post by Miguel Gimenez on April 23, 2026, 09:03:23 am »

Delayed profile spammer rundowndrag reported to moderator.

36

Help / Re: Code editor window closing after saving files (related to very large projects)

« Last post by Stratelier on April 23, 2026, 02:03:11 am »

Oh I've definitely encountered "memory thrashing" before (starting around >90% RAM usage), but when it happens it is typically far worse than what I'm seeing here with CB.

As for ordinary day-to-day usage, I know this bug cast a rather bad first impression of the editor, but I'm also noticing various little mundane details that don't sit as well with me.  Like the top-level split between .c and .h files in the project panel.

I'm willing to help stay and debug for a bit, but I'd probably need instruction on building CB from its source first because as long as I'm the only one it's actively happening to, I'm also the only one that can truly dive into it to research what is going wrong where.

I can find no code that saves the files ok and then closes them.

If I have two files open & modified, the "save changes?" prompt is a good breakpoint where I should be able to fetch the call stack and find exactly WHERE it is trying to close the editor window.

In the meantime, viewing Task Manager there is a "normal" CPU spike while saving a file (in 1 of 4 CPU cores) but it is very localized to CB itself (not affecting other processes / system at large).  I additionally sometimes see the little "leaf" icon next to its status, indicating that (as a UWP process) the system has occasionally suspended it (by force?) -- see attachment.

37

Help / Re: c++23

« Last post by killerbot on April 22, 2026, 10:24:32 pm »

my advice: don't use pcm.


I have several projects using C++23 in CB, even C++26.

38

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by Miguel Gimenez on April 22, 2026, 11:44:29 am »

Profile spammer olenna reported to moderator.

39

General (but related to Code::Blocks) / Re: Generate a file '*_linux.cbp' to '*_win.cbp' or vice versa

« Last post by olenna on April 22, 2026, 11:13:07 am »

There is no official tool that reliably converts a *_linux.cbp project into a *_win.cbp.

40

Help / Re: Cannot find the compiler

« Last post by thereforerepair on April 22, 2026, 10:17:41 am »

Go to Settings -> Compiler, select the "Toolchain executables" tab and fill the controls with your compiler's location (use where gcc.exe in the cmd prompt) and program's names.

Great! The instructions shared are accurate. Executing the correct command is crucial to ensuring the program works and runs.