Recent Posts

Pages: 1 2 3 4 5 6 [7] 8 9 10
61
Using Code::Blocks / Re: debugger plugin's tip windows does not show content with horizontal scroll bar
« Last post by ollydbg on October 28, 2025, 06:13:07 am »
Not the debug tip window, sometimes, the code completion tip(from the clangd_client plugin) window becomes extremely large, see the blow two screen shot, the tip window cover the whole C::B window, also the tip window extended to another screen.  :(
62
Nightly builds / Re: The 25 October 2025 build (13754) is out.
« Last post by Xaviou on October 27, 2025, 07:16:23 pm »
Hi.

32 bits version for Windows can be downloaded from my website.

Debian Trixie (64 bits) and Bookworm (32 and 64 bits) can be installed from my repo
The corresponding unsigned deb files can also be downloaded from the website page linked above.

Ubuntu-22.04, 24.10, 25.04 and 25.10 versions can be installed from my ppa (they are now available for both amd64 and arm64 architectures).

Regards
Xav'
63
General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer
« Last post by alfredo on October 27, 2025, 12:29:03 pm »
Quote from: nenin on October 27, 2025, 12:21:19 pm
You can go to C::B menu Setting/Compiler and inspect "Global Compiler Settings"/"Toolchain executables" for "Selected compiler"

It is correct C:\Program Files\CodeBlocks\MinGW. This is very strange.
64
General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer
« Last post by nenin on October 27, 2025, 12:21:19 pm »
You can go to C::B menu Setting/Compiler and inspect "Global Compiler Settings"/"Toolchain executables" for "Selected compiler"
65
Using Code::Blocks / Problem with standalone exe
« Last post by bad_terminal on October 26, 2025, 10:31:14 pm »
Good evening,

So I've been using CodeBlocks for a number of years while attempting to learn C++. However, after a recent re-installation of 20.03, I noticed that while my programs compile in the editor, the exe's they produce are smaller than usual (215kb v 2487kb), and the standalone exe will not run.

If my understaniding is correct, it's because certain compiler flags weren't set.

Now, whilst I appear to have remedied this, what would cause this to happen? Are those flags not set as default with a fresh installation? I installed 20.03 the first time so long I don't remember having to set flags.

For anyone else having the same problem , the flags I had to set were -static -static-libgcc -static-libstdc++   in the compiler flags section

Also, in the global compiler section. there are numerous things to 'set' eg, C++ compiler , linker for dynamic libs, linker for static libs, resource compiler, make program.

I've set all these to x86_64-w64-mingw32-g++.exe, but really have no idea what any of them are meant to be set to, and/or what the effects of using different (but similarly named) compliers would have.

Please advise.
Thankyou.

So several days and no replies? A veritable hive of activity! Surely somebody knows what all those different 'compliers' are and what the difference is?
66
Nightly builds / The 25 October 2025 build (13754) is out.
« Last post by killerbot on October 26, 2025, 06:50:03 pm »
We switched to gcc 15.1.0 (on 23 May 2025) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/15.1.0posix-12.0.0-ucrt-r1/winlibs-x86_64-posix-seh-gcc-15.1.0-mingw-w64ucrt-12.0.0-r1.7z

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx328_2D_gcc1510-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls15.1.0.7z


The 26 October 2025 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2025/CB_20251026_rev13754_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

  • Clangd_client: Apply Christo patch #1559 for makefiles (Thanks christo)
  • BrowseTracker: Apply JumpTracker.h assert fix (Thanks Christo and Letartare)
  • dragscroll: version 1/4/15 251020 Remember the original (current) mouse position for other events to use.

Regressions/Confirmed/Annoying/Common bugs:


    67
    Using Code::Blocks / Re: debugger plugin's tip windows does not show content with horizontal scroll bar
    « Last post by ollydbg on October 26, 2025, 08:29:09 am »
    Thanks. Can we dynamically change the outer window size? Well, we still need to find a way to fix such issue, though this is not a big issue.  :)
    68
    General (but related to Code::Blocks) / Re: forums.codeblocks.org Cert has expired
    « Last post by ollydbg on October 26, 2025, 08:25:13 am »
    Quote from: Wkerry on October 25, 2025, 07:30:56 am
    New cert has an expiry date of:
    - Thu, 22 Jan 2026 15:46:40 GMT

    Thanks, I will report to our site admin about this.
    69
    General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer
    « Last post by alfredo on October 25, 2025, 06:44:04 pm »
    Quote from: gd_on on October 25, 2025, 12:44:41 pm
    You seem to have two paths for compilers :
    C:\mingw-w64\mingw64
    and
    C:\Program Files\CodeBlocks\MinGW
    Both are used in the working test, for compiling (two sub \include paths) and for linking (two sub \lib paths).
    Normally, you should have only one \include path and one \lib path. Two paths may give conflicts, especially if they are different.

    The second compiler path, is, I suppose, for the installed compiler distributed with Code::Blocks (winlibs 14.2). How did you obtain the content of C:\mingw-w64\mingw64 ?
    And how is configured your "GNU GCC Compiler" and your "GNU GCC MinGW64 Compiler".
    As I saided previously, it looks like you have two compilers installed in two different places. But I'm not on your PC and cannot check this for you.

    I don't have access to that computer at the moment, so I'll have to check. However, I usually download Codeblocks from its website or install it via Chocolatey, and I've never had this kind of problem.
    On my main computer, I installed Windows 11 25H2 via VirtualBox and Codeblocks via Chocolatey, and it compiled the same code with the correct 64-bit compiler without changing any settings, as it should.

    Code
    -------------- Clean: Debug in Test (compiler: GNU GCC Compiler)---------------

    Cleaned "Test - Debug"

    -------------- Build: Debug in Test (compiler: GNU GCC Compiler)---------------

    g++.exe -Wall -fexceptions -g  -c C:\Users\user\test\main.cpp -o obj\Debug\main.o
    g++.exe  -o bin\Debug\test.exe obj\Debug\main.o   
    Output file is bin\Debug\test.exe with size 109.55 KB
    Process terminated with status 0 (0 minute(s), 3 second(s))
    0 error(s), 0 warning(s) (0 minute(s), 3 second(s))
    70
    General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer
    « Last post by gd_on on October 25, 2025, 12:44:41 pm »
    You seem to have two paths for compilers :
    C:\mingw-w64\mingw64
    and
    C:\Program Files\CodeBlocks\MinGW
    Both are used in the working test, for compiling (two sub \include paths) and for linking (two sub \lib paths).
    Normally, you should have only one \include path and one \lib path. Two paths may give conflicts, especially if they are different.

    The second compiler path, is, I suppose, for the installed compiler distributed with Code::Blocks (winlibs 14.2). How did you obtain the content of C:\mingw-w64\mingw64 ?
    And how is configured your "GNU GCC Compiler" and your "GNU GCC MinGW64 Compiler".
    As I saided previously, it looks like you have two compilers installed in two different places. But I'm not on your PC and cannot check this for you.
    Pages: 1 2 3 4 5 6 [7] 8 9 10