Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Development / Re: which standard to use, both for building wx and CB
« Last post by killerbot on Today at 05:18:01 pm »
can you point me to some of that chinese C++17 code ?

C++17/20/23 when correctly applied make code more easy, less buggy. I have used C++17 features for nearly 8 years now, and C++20 features for like 5 years.
And a limited set of C++23 features for like 2 years.

So I am curious to see if that code can be improved and become less Chinese :-)
2
Development / Re: which standard to use, both for building wx and CB
« Last post by Miguel Gimenez on Today at 03:43:49 pm »
I just say that the code, being C++11, already has C++17 parts (cosmetic, fortunately).

Personally I am comfortable with C++11 and some C++17 code is like chinese to me, but obviously having more tools is good.
3
Using Code::Blocks / Re: Something changed on W11 25H2 64b about C library RTL 32b (like "crtdll.dll").
« Last post by ThierryD on Today at 03:38:56 pm »
Hi,

I only change CB version with last "nigthly build" (sorry, not last but previous nigthly ...) :

Name                    : Code::Blocks
Version                 : svn-r13831
SDK Version             : 2.25.0
Scintilla Version       : 3.7.5
Author                  : The Code::Blocks Team
E-mail                  : info@codeblocks.org
Website                 : https://www.codeblocks.org
OS                      : Windows 11 (build 26200), 64-bit edition
Scaling factor          : 1.000000
Detected scaling factor : 1.000000
Display PPI             : 96x96
Display count           : 1
Display 0 (\\.\DISPLAY1): XY=[0,0]; Size=[1920,1080]; Primary

And, all seem OK today ... with Borland C/C++ 5.5.1 and it use into CB.

Mystery of computing science ?!?   GRRRRR !

You can close this topic.

Thierry D.

PS : And thank all CB developers and Xaviou to provide and generate respectively also "nigthly" binary version of CB on Debian/Ubuntu like systems (for me "*.deb" package).
4
Development / Re: which standard to use, both for building wx and CB
« Last post by killerbot on Today at 02:13:16 pm »
Thanks, that's probably what I ran into.


I can understand we get more warnings when using more modern compilers and C++ standard.
In my professional live, I always go for 0 warnings.
But I think CB was never without warnings, so frmo that point of view I would tend to think this should not be a blocker, and we gradually can start fixing the warnings.
Or am I missing something ?
5
Development / Re: which standard to use, both for building wx and CB
« Last post by Miguel Gimenez on Today at 01:04:46 pm »
Quote
Thoug I am not sure, I remember seeing passing by some discussion of stepping up to C++17 ?

Some code is generating warnings due to usage of C++17 features, p.e. [[falltrough]] usage in clangd_client. This change was intended to remove warnings but created others.

Quote
on the second (or third launch), nearly all panels (management, logs & others, ..)and toolbars were gone. Reactivating them manually, all seems fine again.
Restarted CB a few times, all still ok it seems.

wx3.3 changed the format used for saving the layout: if you open C::B compiled with wx3.3, close it (saving the layout explicitly or automatically) and then open C::B compiled with wx3.2 you will loose the layout.
6
Development / which standard to use, both for building wx and CB
« Last post by killerbot on Today at 12:01:55 pm »
Thoug I am not sure, I remember seeing passing by some discussion of stepping up to C++17 ?
Looking at the cbp file for wx32, I see it is at gnu++11 :-( .
I was already building for years wx itself with -std=c++11.

Now what did I just do today:
* build wx 332  (-std=c++11)
* build CB with that using the "CodeBlocks_wx33_64.workspace", which asked for a standard version, I went for -std=c++17 (so no gnu extensions), I already had put the wx global var wx33_64.

Outcome:
* built without a problem
* CB launches fine

WTF:
* on the second (or third launch), nearly all panels (management, logs & others, ..)and toolbars were gone. Reactivating them manually, all seems fine again.
Restarted CB a few times, all still ok it seems.

Question:
* already for a few months when I open the CB workspace, I always pops up a dialog to select the target (src is always preselected), so I just press ok. Is this a regression or a feature we introduced ?


Proposals for building the nighlies, this is controlled and we can do whatever we want: (in the hope it all builds and runs fine)
* build wx dll with -std=c++23, while doing the step-up to wx 3.3.2
* build CB with -std=c++23
* if 23 fails, try 20

Anyone aware of blocking bugs for using wx 3.3.2 ?

Proposal for evolution of the codebase
* switch to C++20, make this an internal firm requirement and allow us to use C++20 features, in the end we are like 6 years late ;-)
* no longer support older envrionments who can not adhere to this requirement
* ditch 32 bit, we have an official release from last year which is still 32 bit, I would say, this was the last one
* maybe even go to c++23 ? That would be my personal preference.

What do you think ?
7
Nightly builds / Re: The 09 April 2026 build (13831) is out.
« Last post by killerbot on Today at 10:37:40 am »
so don't forget  to downloaded the updated mingw and wx dlls !!!!!!!!!!!!!!!!!
8
Nightly builds / The 09 April 2026 build (13831) is out.
« Last post by killerbot on Today at 10:36:47 am »
We switched to gcc 15.2.0 (on 09 April 2026) --> 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.2.0posix-14.0.0-ucrt-r7/winlibs-x86_64-posix-seh-gcc-15.2.0-mingw-w64ucrt-14.0.0-r7.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_gcc1520-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls15.2.0.7z


The 09 April 2026 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2026/CB_20260409_rev13831_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

  • no functional changes, building with gcc 15.2.0

Regressions/Confirmed/Annoying/Common bugs:


    9
    Nightly builds / Re: The 08 April 2026 build (13831) is out.
    « Last post by Xaviou on Yesterday at 09:37:11 pm »
    Hi.

    32 bits version for Windows (and also 64 bits version) can be downloaded from my website.
    I made both a wxWidgets-3.2.10 and wxWidgets-3.3.2 linked versions

    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 and 26.04 versions can be installed from my ppa (they are now available for both amd64 and arm64 architectures).

    Regards
    Xav'
    10
    Using Code::Blocks / Re: Something changed on W11 25H2 64b about C library RTL 32b (like "crtdll.dll").
    « Last post by ThierryD on Yesterday at 04:31:39 pm »
    And today, I try to resolve this "last" problem ...

    I change option "-v" by "/v" into Tab "Another linker options" into CB project, result next :

    Code
    cmd /c bcc32 | grep Borland          
    File STDIN:
    Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
    bcc32.exe -q  -w -tW -6 -y -v -D_DEBUG -DDEBUG    -IC:\BCC55\include -IC:\bccsdk\include -oobjBC55\Debug\src\Lesson03.obj -c src\Lesson03.c
    brcc32.exe -32 -foobjBC55\Debug\src\Lesson03.res -IC:\BCC55\include -IC:\bccsdk\include -d_DEBUG -dDEBUG  src\Lesson03.rc
    ilink32.exe -q -aa  /v  -LC:\BCC55\lib\psdk -LC:\BCC55\lib c0w32 objBC55\Debug\src\Lesson03.obj,binBC55\Debug\Lesson03.exe,,import32.lib cw32mti.lib opengl32.lib glu32.lib gdi32.lib winmm.lib user32.lib kernel32.lib,,objBC55\Debug\src\Lesson03.res
    Borland Resource Compiler  Version 5.40
    Copyright (c) 1990, 1999 Inprise Corporation.  All rights reserved.
    src\Lesson03.c:
    Warning W8060 src\Lesson03.c 386: Possibly incorrect assignment in function CreateGLWindow
    Warning W8071 src\Lesson03.c 406: Conversion may lose significant digits in function CreateGLWindow
    Warning W8060 src\Lesson03.c 408: Possibly incorrect assignment in function CreateGLWindow
    Warning W8060 src\Lesson03.c 429: Possibly incorrect assignment in function CreateGLWindow
    Warning W8057 src\Lesson03.c 591: Parameter 'hInstance' is never used in function WinMain
    Warning W8057 src\Lesson03.c 591: Parameter 'hPrevInstance' is never used in function WinMain
    Warning W8057 src\Lesson03.c 591: Parameter 'lpCmdLine' is never used in function WinMain
    Warning W8057 src\Lesson03.c 591: Parameter 'nCmdShow' is never used in function WinMain
    Error: Error processing module src\Lesson03.c
    Process terminated with status 2 (0 minute(s), 1 second(s))
    0 error(s), 8 warning(s) (0 minute(s), 1 second(s))
    Build log saved as: 
    file://C:/src/OpenGL/NeHe_Lesson03-master/Lesson03_build_log.html

    Ok, not resolve, but if I reproduce instructions in command console (only linkage without change ... exact syntax, ... because compilation of C source file and resource file are correct ...) :

    Code
    set PATHSAV=%PATH%
    set PATH=C:\BCC55\bin;%PATH%
    ilink32.exe -q -aa  /v  -LC:\BCC55\lib\psdk -LC:\BCC55\lib c0w32 objBC55\Debug\src\Lesson03.obj,binBC55\Debug\Lesson03.exe,,import32.lib cw32mti.lib opengl32.lib glu32.lib gdi32.lib winmm.lib user32.lib kernel32.lib,,objBC55\Debug\src\Lesson03.res

    ... work perfectly ...

    I don't understand it !  In CB, link fail, in command console, not. What is difference (open "console" into CB code) ?

    Return in "stable state" on my WIN11 configuration with "suppress "update" of march 2026. Why not ...

    Someone meet same problem ?

    Thank's. 
    Pages: [1] 2 3 4 5 6 ... 10