Recent Posts

1

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

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

Thanks.
This effectively removes the warning.

2

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

« Last post by Miguel Gimenez on Today at 04:53:11 pm »

This section in debugger_gdbmi_wx32-unix.cbp looks out of place:

Code

<Extensions>
			<envvars set="cb_plugin" />
			<wxsmith version="1">
				<gui name="wxWidgets" src="" main="" init_handlers="necessary" language="CPP" />
				<resources>
					<wxPanel wxs="wxsmith/config_panel.wxs" src="src/config.cpp" hdr="src/config.h" fwddecl="1" i18n="1" name="ConfigurationPanel" language="CPP" />
				</resources>
			</wxsmith>
		</Extensions>

3

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

« Last post by LETARTARE on Today at 03:23:59 pm »

Context :Leap-15.6, gcc-15.2.0, wx-328, gtk3

Compilation of : ContribPlugins_wx32-unix.workspace => correct

By wanting to reload the default workspace I received this message (attached) , which I could not solve.

I couldn't find anything in 'Envars-wx3.2.x(Unix)'

4

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

« Last post by Miguel Gimenez on Today at 02:55:02 pm »

Debugger finished with status 1

This means the debugger found an error and quit without executing your program at all. C::B expects GDB or CDB as debugger, not LLDB, and it uses commands specific for them that LLDB does not understand. Also, it parses answers using regex that will fail with LLDB.

5

Using Code::Blocks / Re: Dark Mode

« Last post by Miguel Gimenez on Today at 11:17:49 am »

Spam reported to moderator.

6

Using Code::Blocks / Re: Dark Mode

« Last post by emmausa on Today at 10:04:12 am »

There is a community project called codeblocks-dark-mode-msw based on a newer version of wxWidgets to enable dark mode on Windows, but this is not an official release of Code::Blocks 25.03. Subway Surfers

7

Help / Debugger lldb.exe exits without running target executable

« Last post by MadDavid on Yesterday at 10:41:33 pm »

I'm trying to get LLVM CLANG working with Code::Blocks.

I've got basic compilation working, now I'm trying to get debugging working.

So I set up a test project called "TestConsoleDebugger", which has the following code

#include <iostream>
#include <cstdio>

int main()
{
    int iterations = 0;
    FILE* fp;

    while (iterations < 1000000)
    {
      iterations++;
    }

    fp = fopen("Debug.txt", "a+");
    fprintf(fp, "Iterations = %i\n", iterations);
    fflush(fp);
    fclose(fp);
    return 0;
}

and breakpoints on "iteration++;" and "fp = fopen("Debug.txt", "a+");

When I click the red "Debug / Continue" arrow, I get

Active debugger config: GDB/CDB debugger:LLVM 64
Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: E:\Development\TestConsoleDebugger\
Adding source dir: E:\Development\TestConsoleDebugger\
Adding file: E:\Development\TestConsoleDebugger\bin\Debug\TestConsoleDebugger.exe
Changing directory to: E:/Development/TestConsoleDebugger/.
Set variable: PATH=.;E:\Compilers\LLVM\bin;E:\Compilers\LLVM;[bunch of irrelevant paths]E:\Compilers\CodeBlocks;\;E:\Compilers\TDM-GCC-64\bin;E:\Compilers\WinSDK\Windows Performance Toolkit;E:\Compilers\Python310\Scripts;E:\Compilers\Python310;E:\Compilers\CodeBlocks\MinGW\bin;E:\Compilers\VisualStudio\VC\Tools\MSVC\14.31.31103\bin\Hostx64\x64;E:\Compilers\Zip
Starting debugger: E:\Compilers\LLVM\bin\lldb.exe -G -lines -2 -y E:/Development/TestConsoleDebugger/; -srcpath E:/Development/TestConsoleDebugger/; E:/Development/TestConsoleDebugger/bin/Debug/TestConsoleDebugger.exe
done
Debugger finished with status 1
Selecting target:
Debug
Adding source dir: E:\Development\TestConsoleDebugger\
Adding source dir: E:\Development\TestConsoleDebugger\
Adding file: E:\Development\TestConsoleDebugger\bin\Debug\TestConsoleDebugger.exe
Changing directory to: E:/Development/TestConsoleDebugger/.
Set variable: PATH=.;E:\Compilers\LLVM\bin;E:\Compilers\LLVM;[bunch of irrelevant paths]E:\Compilers\CodeBlocks;\;E:\Compilers\TDM-GCC-64\bin;E:\Compilers\WinSDK\Windows Performance Toolkit;E:\Compilers\Python310\Scripts;E:\Compilers\Python310;E:\Compilers\CodeBlocks\MinGW\bin;E:\Compilers\VisualStudio\VC\Tools\MSVC\14.31.31103\bin\Hostx64\x64;E:\Compilers\Zip
Starting debugger: E:\Compilers\LLVM\bin\lldb.exe -G -lines -2 -y E:/Development/TestConsoleDebugger/; -srcpath E:/Development/TestConsoleDebugger/; E:/Development/TestConsoleDebugger/bin/Debug/TestConsoleDebugger.exe
done
Debugger finished with status 1

Code::Blocks does not stop at any breakpoints, the console does not appear, and notably, "Debug.txt" does not appear.  When I click the green "Run" arrow, in contrast, it pops up the console and "Debug.txt" appears in the project directory.

Is there any advice for how to get lldb to actually debug from Code::Blocks?  E.g., do I need to put anything in for "Debugger initialization commands" in the debugger setting?

8

General (but related to Code::Blocks) / Re: r13922 .cbp Option object_output usage

« Last post by Pecan on Yesterday at 06:42:50 pm »

At least for debugger_gdbmi_wx32_64.cbp and debugger_gdbmi_wx33_64.cbp, it might be better to pluralize the object_output reference as all other wx32_64.cbp and wx33_64.cbp files do.  For instance, change

Code

<Option object_output="../../../.obj33_64/plugins/contrib/debugger_gdbmi" />

to

Code

<Option object_output="../../../.objs33_64/plugins/contrib/debugger_gdbmi" />

in the file debugger_gdbmi_wx33_64.cbp

Done. Thanks.

9

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

« Last post by Xaviou on Yesterday at 05:30:59 pm »

Hi.

@Xaviou, I could not reproduce the compilation error in clangd_client when compiled against wxWidgets-3.2.11. May be due to difference in configurations. Missing header include is added in svn rev 13925, hope it will fix the issue.

It does : thank you. I've replaced the rev13924 archives by rev13925 ones for download

Could you please provide steps to reproduce error on building for Ubuntu-26.04 on launchpad? Is this something we can replicate locally?

I just use an updated old made script : here is its content:

Code: sh

#!/bin/sh
cd ~/codeblocks/sources

if [ "x$1" != "xcurrent" ]; then
  rm debian/changelog
  if [ "x$1" != "x" ]; then
    svn update --revision $1 .
  else
    svn update .
  fi;
fi;

if [ -f ./.last_revision ]; then
	rm ./.last_revision
fi
../00_update_revision.sh 26.04.1

sed -i 's/UNRELEASED/resolute/' ./debian/changelog

echo 10 > debian/compat
echo Running Bootstrap...
./bootstrap

echo Running debian/setup_control.sh
./debian/setup_control.sh resolute

echo Running Debuild...
debuild -S -sa -d -us -uc
cd ..

The "00_update_revision.sh" script is just a copy of the one include in codeblocks sources witch changes the final name of the archives (line 59)

Code

dch -v 25.03+svn$REV~ubuntu$1 "New svn revision"

I then obtain the sources packages only : I then sign them and upload them to launchpad and the build starts automatically.

Regarding the 26.04 failure, Gemini says:

The reason it fails on Ubuntu 26.04 is that the Common Debian Build System (cdbs) package officially dropped and deleted the deprecated autotools.mk and makefile.mk files.
If you control the source code of the project or package, the best fix is to stop using cdbs with the old autotools.mk include. Instead, rewrite your debian/rules file to use modern, clean dh (Debhelper) syntax, which handles autotools automatically.

I'll try to have a look at this ASAP : thank you.

Regards
Xav'

10

General (but related to Code::Blocks) / Re: r13922 .cbp Option object_output usage

« Last post by Miguel Gimenez on Yesterday at 01:19:29 pm »

Related to this, r13922 included the new debugger_gdbmi* projects in the ContribPlugin* workspaces, but not in the main ones.