Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
Development / dpi aware v2?
« Last post by ollydbg on Today at 02:47:35 pm »
In the src target, we have a src\resources\resources.rc, which contains such code:

  #if defined(WX_CPU_AMD64)
    #if defined(cbDPI_AWARE_ON)
        wxMANIFEST_ID RT_MANIFEST "amd64_dpi_aware_on.manifest"
        #warning Manifest: amd64_dpi_aware_on.manifest
        wxMANIFEST_ID RT_MANIFEST "amd64.manifest"
        #warning Manifest: amd64.manifest

When in a win 10 PC, I have first monitor which is DPI125%, and a second monitor has DPI 100%. Now if I start C::B in the first monitor, and drag the window to the second monitor, the main window get blurring, so do we need dpi aware v2?

If I under correctly, the v2 version should have dpi for each monitor, see document here:

High DPI Desktop Application Development on Windows - Win32 apps | Microsoft Learn

Any ideas?

yeah exactly what I mean, it's not easy to do in codeblocks, but alright. Love codeblocks for some reason for  c programming...vs code s###s for c programming.
Nightly builds / Re: The 18 February 2023 build (13215) is out.
« Last post by boojai2 on Today at 04:46:52 am »
thanks! it works!
Perfect, the fix to disable the ESC-sequences works fine.
Now can I set/delete the breakpoints and als the watches are displayed nice.

I also dont unterstand why C::B trys to write there. I added the rights, so that C::B can write there and I added also the directory tree, but nothing.

I deleted again all from C::B and searched also the registry and deleted all. Also a complete search on the hard drive and deleted all with relation to C::B by hand.

After a new istallation it works.

Many thanks for the help.

@Miguel and thanks for PM (the help with the postings)
That is a problem with the GDB version you are using, it colorizes the output using ANSI escape sequences unexpected by C::B.

It is fixed in trunk, if you want to fix 20.03 see this forum thread

EDIT: About saving config, recent Windows (W7+) do not allow writing under Program Files. I do not know why 17.12 tries to write there, but it will not work unless you execute C::B as administrator.
Help / C::B could not save settings Debugger looks strange and dont work
« Last post by seahawkibiza on Yesterday at 04:32:59 pm »
I have a problem with C::B.
I installed the 20.3, but there the debugger dont work.
(See picture). Also I cant remove breakpoints.

But on 17.12, the last version I have, I can not save the config.
Nightly builds / Re: The 18 February 2023 build (13215) is out.
« Last post by Miguel Gimenez on Yesterday at 09:29:46 am »
The DLL and the unzip instructions are only for Windows, use just the DMG file (I do not know how a DMG is used, but should be straightforward).
Nightly builds / Re: The 18 February 2023 build (13215) is out.
« Last post by boojai2 on Yesterday at 06:04:37 am »
Hi everyone,

I am absolute newbie here and trying to learn C and C++. I'm using mac OS and having a hard time getting codeblocks working on my computer.
I am using OSX 13.2.1.
I was following this post and trying to get nighty C::B working on my computer. I have tried the MacPorts way but C::B was not functioning properly (reversed colour).

From what I am reading, I need to download CB_20230218_rev13215_macOS-11.6_x64-wx3.1.6.dmg, CB_20230218_rev13215_wx32_win64.7z from the google drive below. And wxWidge dll, Mingw64 dll from the first post.

And now I'm confused about the next steps.
1) unzip the CB nightly in some directory - the dmg that I can download does not need to be unzipped??
2) unzip both ddl's into the same directory where I unzipped the nighty.

Can someone please help me with my first step in learning C and C++?  :'(

Thanks in advance!


OS X version of this rev can be downloaded from my Google Drive.
There is only a macOS-11.6 version.
Note that it is not a notarized version of the application.

32 bits version for Windows can also be found in the same place.

Debian Buster and Bullseye (32 and 64 bits) can be installed from my repo.

Announcements / Re: Remote Debugging: "Interrupting debugger failed :("
« Last post by ollydbg on March 26, 2023, 04:52:10 pm »
I'm not fully understand the code change in rev

If I remember correctly, many years ago, under C::B, I can use gdb.exe to connect with gdbserver.exe, and use gdbserver.exe to debug(control) a local exe file.

Many embedded development need remote debugging feature, so this is a big regression.

I modify the Code::Blocks' opencv project wizard to linking msys2's opencv library(currently, its opencv4)

I put the wizard.script here:

Also, the source code should be updated like below:

#include <opencv2/core/core.hpp>
#include <opencv2/imgproc/imgproc.hpp>
#include <opencv2/highgui/highgui.hpp>
using namespace cv;

int main(int argc, char *argv[])
    Mat img = imread("arnold_schwarzenegger.jpg", IMREAD_COLOR);
       return -1;
    namedWindow("arnold_schwarzenegger", WINDOW_AUTOSIZE );
    imshow("arnold_schwarzenegger", img);
    return 0;

The IMREAD_COLOR and WINDOW_AUTOSIZE is new options for opencv4. Our old wizard using the opencv2 options.
Pages: [1] 2 3 4 5 6 ... 10