Recent Posts

1

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

« Last post by Miguel Gimenez on Today at 10:26:36 am »

Fixed in r13927.

2

General (but related to Code::Blocks) / Re: Thanks for a great IDE

« Last post by Miguel Gimenez on Today at 10:20:08 am »

Spam reported to moderator.

3

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

« Last post by Suryavarman on Today at 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?

4

General (but related to Code::Blocks) / Re: Thanks for a great IDE

« Last post by snowrider3dgame on Today at 08:55:11 am »

Snow Rider 3D offers a relaxing yet challenging entertainment experience, where each playthrough is an opportunity to hone your skills, improve your reflexes, and conquer new score milestones.

5

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

« Last post by Pecan on Yesterday at 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.

6

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

« Last post by christo on Yesterday at 07:52:45 pm »

     - Error clangd client : A path containing clang has not been found (seem easy to resolve : add this path into settings clangd client with menu indicated)

Hi @ThierryD, could you please share the path of  clangd binary? It should be autodetected if it is in standard paths, else it is a bug.

     - An assertion failed! ./src/unix/fswatcher_inotify.cpp(66): assert in init(): File system watcher needs an event loop (I bypass this by click on "continue" button)

I could not reproduce the crash in ubuntu 24.04 with Xaviou's ppa (25.03+svn13924~ubuntu24.04.1). Is this issue seen only once, or is it seen on when ever codeblocks is opened?

7

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

« Last post by MadDavid on Yesterday at 07:29:23 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?

8

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

« Last post by Xaviou on Yesterday at 06:55:44 pm »

Hi.

Just two signals about this last nightly (13924) on Linux Mint 22.3 Zena (near Ubuntu 24.04)
     - Error clangd client : A path containing clang has not been found (seem easy to resolve : add this path into settings clangd client with menu indicated)
     - An assertion failed! ./src/unix/fswatcher_inotify.cpp(66): assert in init(): File system watcher needs an event loop (I bypass this by click on "continue" button)

The second signal is also a problem with the Clangd_Client plugin (tested on Debian: the message appears if the plugin is enabled)

Regards
Xav'

9

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

« Last post by ThierryD on Yesterday at 06:32:28 pm »

Hi Xaviou,

Just two signals about this last nightly (13924) on Linux Mint 22.3 Zena (near Ubuntu 24.04)
     - Error clangd client : A path containing clang has not been found (seem easy to resolve : add this path into settings clangd client with menu indicated)
     - An assertion failed! ./src/unix/fswatcher_inotify.cpp(66): assert in init(): File system watcher needs an event loop (I bypass this by click on "continue" button)

and CB start "normally" ...

Regards.

PS : cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=22.3
DISTRIB_CODENAME=zena
DISTRIB_DESCRIPTION="Linux Mint 22.3 Zena"

10

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

« Last post by LETARTARE on Yesterday at 05:14:55 pm »

Thanks.
This effectively removes the warning.