Recent Posts

1

Help / Re: Used .deb files to install Codeblocks

« Last post by stahta01 on Yesterday at 08:01:01 pm »

https://forums.codeblocks.org/index.php/topic,26198.msg178144.html#msg178144

Maybe this link will help you.

I know a decade ago it would have been enough to help me; but I have forgotten how to use the info since then between old age and COVID I have lost too many memories.

Tim S.

2

Help / Used .deb files to install Codeblocks

« Last post by ErBee on Yesterday at 02:20:09 pm »

Hi there,

I've installed Cobeblocks from de 25.03 .dev files from the Codeblocks site. 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. 

3

Development / Re: special handling of the macro replacement ""?

« Last post by ollydbg on January 30, 2026, 10:53:50 am »

Have a look at https://sourceforge.net/p/codeblocks/tickets/1188/ .....

I looked at your patch file in the above link, it is a bit complex, I think my patch is much simple, we can just leave the gcd variable as empty.

4

Development / Re: special handling of the macro replacement ""?

« Last post by AndrewCot on January 30, 2026, 10:41:01 am »

Have a look at https://sourceforge.net/p/codeblocks/tickets/1188/ .....

5

General (but related to Code::Blocks) / Re: Code::Blocks 25.03: Debugger fails to catch breakpoints in inline/template-enhan

« Last post by ollydbg on January 30, 2026, 04:21:11 am »

I think your issue is not Code::Blocks related.

Because Code::Blocks just send commands by driving the gcc to compile, and drving the gdb to debug, so you can looked at the compiler plugin full log and debugger plugin full log to know all the communications.

6

General (but related to Code::Blocks) / Code::Blocks 25.03: Debugger fails to catch breakpoints in inline/template-enhan

« Last post by promotebrilliant on January 30, 2026, 03:53:05 am »

I'm using Code::Blocks 25.03 with GCC 12/13 and a project configured by CMake to build with multiple template/inline modules. After a successful build, when I run the debugger:
Breakpoints in inline/template functions (especially when called from template specialization) sometimes only jump once or don't catch at all, even with the debug symbol.
While breakpoints in other normal code (non-template/inline) work perfectly fine.

I've enabled -g3 and no optimization (), and CMake verifies that debug info is included in the binary.
Has anyone else encountered a similar problem in Code::Blocks?

Is this a bug related to how CB's GDB/Debugger handles template/inline symbols?

Are there any settings in Settings → Debugger or Project that I'm missing?

Thanks everyone!

7

Development / Re: special handling of the macro replacement ""?

« Last post by ollydbg on January 29, 2026, 04:53:05 am »

Oh, I change the mind, it looks like this patch should solve the issue, see here:

* sdk: try to handle empty valued members in global compiler variable

8

Development / Re: special handling of the macro replacement ""?

« Last post by ollydbg on January 29, 2026, 04:10:26 am »

I did some test, and if the empty value key is allowed to add in the global compiler variable, the result may be that there are a lot of predefined keys saved to the config file, for example, see below:

Code

		<sets>
			<default>
				<cccccc>
					<DDD>
						<str>
							<![CDATA[]]>
						</str>
					</DDD>
					<BBB>
						<str>
							<![CDATA[xxx]]>
						</str>
					</BBB>
					<CFLAGS>
						<str>
							<![CDATA[]]>
						</str>
					</CFLAGS>
					<BIN>
						<str>
							<![CDATA[]]>
						</str>
					</BIN>
					<LFLAGS>
						<str>
							<![CDATA[]]>
						</str>
					</LFLAGS>
					<OBJ>
						<str>
							<![CDATA[]]>
						</str>
					</OBJ>
					<LIB>
						<str>
							<![CDATA[]]>
						</str>
					</LIB>
					<INCLUDE>
						<str>
							<![CDATA[]]>
						</str>
					</INCLUDE>
					<BASE>
						<str>
							<![CDATA[aaaa]]>
						</str>
					</BASE>
				</cccccc>

You can see, I don't want to do that DDD is a user defined key, and its value is empty. While the CFLAGS is predefined key, and its value is also empty.

So, I think the solution is: using the predefined value string, for example, a value named: __EMPTY__ or just an empty string "", then in the code when we get the value, we have to check the result, and remove the __EMPTY__ or "" in the command line.

9

General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!

« Last post by rjmolloy on January 28, 2026, 08:27:21 pm »

I'm here and I'm real and really like C::B.

10

Development / Re: special handling of the macro replacement ""?

« Last post by gd_on on January 28, 2026, 05:54:21 pm »

To add some informations:
In standard cbp files, there is an environment variable defined as:

Code

<Variable name="WX_CFG" value="" />

When it is used in standard cbp files, as:

Code

<Add directory="$(#wx33_64.lib)/gcc_dll$(WX_CFG)

there are no problems.

In my unified workspace/cbp files, I define a wxwidgets path as, in my case, C:\wxWidgets-3.3.1 as the base, and in a user-defined field, I have created a wx_cfg variable. If I set this variable with nothing (an empty field), the variable is eliminated after a click on the save button. It's why, as in standard cbp files, I tried to set an empty string by "". Apparently, this is the problem described by ollydbg when I use a variable as:

Code

<Add directory="$(#WXWIDGETS)/lib/gcc_dll$(#WXWIDGETS.WX_CFG)