Recent Posts

31

Help / Code::Blocks always add #ifndef HEADER_ on some .h files

« Last post by FredCL on August 04, 2026, 07:47:03 pm »

Hello,

I don't know why on my project only on one file Code::blocks always add
#ifndef HEADER_9598362C9F593684
#define HEADER_9598362C9F593684
at the beginning of the file

the file already have a
#ifndef _FRAMEAPP_H_
#define _FRAMEAPP_H_

The file is encoded in UTF8.
How to avoid this unwanted adding ?

32

Using Code::Blocks / Re: Interest in a CMake Solution Generator for Code::Blocks via cmake-file-api?

« Last post by MehdiChinoune on August 04, 2026, 06:28:53 am »

Of course,
We are waiting for someone to do it since CMake deprecated generating "CodeBlocks" projects.

33

Nightly builds / Re: The 20 July 2026 build (13916) is out.

« Last post by Elena on August 01, 2026, 11:34:01 am »

Gosh ! You really mean "anti-feature" ! As you may have understood, it's not just about the blue line, but they look ugly in general if compared with the previous ones ! Even WX developers are uniforming to those ugly w10+ standards Really CB coders have no control over it, maybe with some attributes ? That's crazy !!

34

Nightly builds / Re: The 27 July 2026 build (13924) is out.

« Last post by ThierryD on July 31, 2026, 05:42:48 pm »

... I have installed WSL on W11 15H2 64 bit, but with last distribution of Ubuntu (available with WSL -> Ubuntu 26.04).

And, I test to use your PPA to download last nightly of CB (after have installed CB 25.03 with "apt").

I execute theses instructions with success :
sudo add-apt-repository ppa:x-psoud/cbnb
sudo apt update

but,  next step, normally "sudo apt upgrade", don't work ...
Nothing about last nightly of CB ...

Can you test this ?

Thank you.

35

Nightly builds / Re: The 27 July 2026 build (13924) is out.

« Last post by ThierryD on July 31, 2026, 05:36:48 pm »

-> to Xaviou too :

On my "new" PC, I ha

36

Nightly builds / Re: The 27 July 2026 build (13924) is out.

« Last post by ThierryD on July 31, 2026, 05:33:36 pm »

... type on "tab" on keyboard do exit/fail on my last topic write ... I continue here :

To Xaviou :
         - my last relaunch of CB without changes into "plugin" don't see last error on assert, only first message about Path ...
         - disable plugin "clangd_client", and new relaunch of CB, no one message appear ... Thank you.

To Christo :
        - I don't use "clangd" on Linux Mint ... at date. Nothing install about this on my configuration.

Regards.

37

Nightly builds / Re: The 27 July 2026 build (13924) is out.

« Last post by ThierryD on July 31, 2026, 05:26:56 pm »

Sorry to late response ... My "old" PC is failed ... and new PC is not fully ready ...

To Xaviou : 
Last relaunch of CB

38

Plugins development / Re: rev-13926 ; ContribPlugins_wx32-unix.workspace

« Last post by Miguel Gimenez on July 30, 2026, 10:26:36 am »

Fixed in r13927.

39

Using Code::Blocks / Interest in a CMake Solution Generator for Code::Blocks via cmake-file-api?

« Last post by Suryavarman on July 30, 2026, 09:47:41 am »

Hello

Do you think there would be interest in creating a module or submitting a pull request to Code::Blocks to generate CMake solutions directly from CB using the cmake-file-api?

40

Help / Re: Debugger lldb.exe exits without running target executable

« Last post by Pecan on July 29, 2026, 09:38:38 pm »

Thanks for your reply.  As I understand it, there's no way to get the LLVM debugger to work with code::blocks (barring going into the C::B source code and implementing support).  Is that correct?

There is already a debugger being developed for CodeBlocks that supports llvm.
The debugger_DAP source is at https://github.com/pecanh/debugger_DAP.
The setup for the debugger is the same as for debugger_gdb or debugger_gdbmi.

Once the plugin is loaded by CodeBlocks, a settings/debugger entry will appear and you will have
to set the location of your debugger (see attachment).

You also have to decide what flavor of breakpoint.symbols to use.

The ususal -g flag alone will not work for llvm.
You have to match the compiler with the gdb symbol types expected.

Look into the compiler setup for the llvm flag types.


Place the source of the debugger_DAP into the contrib plugin folder.
Review the .cbp file to fit your environment.
Compile and place the plugin into the output32_xx.plugin folder or into the devel32_xx folder to test.
You can use the regular debugger_gdb or debugger_gdbmi to debug debugger_DAP if necessary.