Author Topic: The 12 October 2024 build (13584) is out.  (Read 11568 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5519
The 12 October 2024 build (13584) is out.
« on: October 12, 2024, 08:04:48 pm »
We switched to gcc 14.1.0 (on 20 May 2024) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/14.1.0posix-18.1.5-11.0.1-ucrt-r1/winlibs-x86_64-posix-seh-gcc-14.1.0-mingw-w64ucrt-11.0.1-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_wx326_2D_gcc1410-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls14.1.0.7z


The 12 October 2024 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2024/CB_20241012_rev13584_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

  • File manager: Prevent deletion of the system root folder (ticket #1504).
  • CbLauncher: build the CbLauncher.exe in the Makefile.am
  • SmartIndent plugin: disable parallel make for SmartIndent(Thanks stahta01)
  • SDK: codeblocks plugin fix in the case that The MSys2 UCRT64 package gives a false failure message when installing a cbplugin(Thanks stahta01)
  • wxSmith: fix dll symbol export issue when building C::B under msys2's configure/make (Thanks stahta01)
  • src: Use "WX_CPPFLAGS" instead of "WX_CXXFLAGS" in Makefile.am(Thanks stahta01)
  • Clangd_client Apply Linux patch 1503 to eliminate polling and cpu usage. Thanks Christo
  • wxSmith: Make the OK button the default one in wxStdDlalogButtonSizer.

Regressions/Confirmed/Annoying/Common bugs:



    Offline ThierryD

    • Multiple posting newcomer
    • *
    • Posts: 49
    Re : The 12 October 2024 build (13584) is out.
    « Reply #1 on: October 15, 2024, 04:15:53 pm »
    Hi,

    I don't known if cause  of crash is due to "newly" Nightly Build, or if I test CB with new configuration (I used two screens "today" on my laptop to work most quickly with multiple windows), but I constat crash after one click on main menu "Build" in second screen on Windows 11 64b.

    Here my config CB  (and too in attachment)

    Name                    : Code::Blocks
    Version                 : svn-r13584
    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 22631), 64-bit edition
    Scaling factor          : 1.000000
    Detected scaling factor : 1.000000
    Display PPI             : 96x96
    Display count           : 2
    Display 0 (\\.\DISPLAY1): XY=[0,0]; Size=[1920,1080]; Primary
    Display 1 (\\.\DISPLAY4): XY=[1920,0]; Size=[1920,1080];

    wxWidgets Library (wxMSW port)
    Version 3.2.6 (Unicode: wchar_t, debug level: 1),
    compiled at Sep 25 2024 20:12:19

    Runtime version of toolkit used is 10.0.

    NB : two display detected ...

    Join RPT generated.

    Thank's

    TDE.



    Offline Miguel Gimenez

    • Developer
    • Lives here!
    • *****
    • Posts: 1644
    Re: The 12 October 2024 build (13584) is out.
    « Reply #2 on: October 15, 2024, 05:00:06 pm »
    It is not a crash, it is generated by wxWidgets because we are trying to capture an already captured mouse.

    This is a known old problem, but to fix it we need a consistent way to reproduce. If you can reproduce it consistently, please post the steps.

    Offline ThierryD

    • Multiple posting newcomer
    • *
    • Posts: 49
    Re: The 12 October 2024 build (13584) is out.
    « Reply #3 on: October 21, 2024, 04:31:30 pm »
    Hi Miguel,

    Sorry for delay of this response, ...but it's really difficult to reproduce this (not) "crash" of CB (wx is the major cause ...).
    I'm not sure it's the same scenario, but yes today,  another RPT is generate (joined).

    I try to describe my actions (always on my second screen) :
       - after many "rebuild" on Workspace CB, I save "all" with submenu "Save Everything" in menu "File",
       - and last click on "All build" (my virtual target) to "rebuild all"  and crash ...

    I join too my project CB (renamed in *.cbp.txt).

    I reload all of my environment of this project on GitHub here : https://github.com/tdechaize/Lesson10 (repository open).

    Thank's.

    Regards.



    Offline stahta01

    • Lives here!
    • ****
    • Posts: 7699
      • My Best Post
    Re: The 12 October 2024 build (13584) is out.
    « Reply #4 on: October 22, 2024, 01:27:23 am »
    Hi Miguel,

    Sorry for delay of this response, ...but it's really difficult to reproduce this (not) "crash" of CB (wx is the major cause ...).
    I'm not sure it's the same scenario, but yes today,  another RPT is generate (joined).

    I try to describe my actions (always on my second screen) :
       - after many "rebuild" on Workspace CB, I save "all" with submenu "Save Everything" in menu "File",
       - and last click on "All build" (my virtual target) to "rebuild all"  and crash ...

    I join too my project CB (renamed in *.cbp.txt).

    I reload all of my environment of this project on GitHub here : https://github.com/tdechaize/Lesson10 (repository open).

    Thank's.

    Regards.

    This time it looks like code completion crashed; so, it is not the same as last time. I suggest turning off the code completion plugin.
    But, I do not use the old code completion plugin and rarely the new clang plugin replacement.

    Tim S.
    C Programmer working to learn more about C++ and Git.
    On Windows 7 64 bit and Windows 10 64 bit.
    --
    When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

    Offline ThierryD

    • Multiple posting newcomer
    • *
    • Posts: 49
    Re: The 12 October 2024 build (13584) is out.
    « Reply #5 on: October 22, 2024, 03:04:33 pm »
    Ok, Tim, I disabled plugin "Code completion" (and clangd too).

    Thank's.

    Offline Uriens The Gray

    • Multiple posting newcomer
    • *
    • Posts: 12
    Re: The 12 October 2024 build (13584) is out.
    « Reply #6 on: October 26, 2024, 03:17:51 pm »
    Works fine from the MSYS2 packages. Using Win 11.

    Offline ThierryD

    • Multiple posting newcomer
    • *
    • Posts: 49
    Re: The 12 October 2024 build (13584) is out.
    « Reply #7 on: October 26, 2024, 06:45:42 pm »
    Hi Miguel, Hi Tim,

    YES. Today I can reproduce precedent "crash".

    An Alert box appear with title : "wxWidgets Debug Alert"

    Text into this alert box :
       ../../src/commen/wincmn.cpp(3426): assert ""!wxMouseCapture::stack.empty()"" failed into
       ReleaseMouse(): Releasing mouse capture but capture stack empty?
       
    Juste to describe my actions, I modify my project CB, but not in IDE, simply with "notepad++" to add
    two new files at this project (here new files are "logger.h" and "logger.c").

    In my file *.cbp, it's easy to add these new lines under :

          <Unit filename="src/logger.c">
             <Option compilerVar="CC" />
             <Option target="Debug Mingw32 official" />
             <Option target="Release Mingw32 official" />
             <Option target="Debug Mingw64 CB" />
             <Option target="Release Mingw64 CB" />
             <Option target="Debug Mingw64 Dev-Cpp" />
             <Option target="Release Mingw64 Dev-Cpp" />
             <Option target="Debug CYGWIN 32" />
             <Option target="Release CYGWIN 32" />
             <Option target="Debug CYGWIN 64" />
             <Option target="Release CYGWIN 64" />
             <Option target="Debug CYGWIN N64" />
             <Option target="Release CYGWIN N64" />
             <Option target="Debug Mingw32 wl" />
             <Option target="Release Mingw32 wl" />
             <Option target="Debug Mingw64 wl" />
             <Option target="Release Mingw64 wl" />
             <Option target="Debug TDM MinGW32" />
             <Option target="Release TDM MinGW32" />
             <Option target="Debug TDM MinGW64" />
             <Option target="Release TDM MinGW64" />
             <Option target="Debug MSYS2W32" />
             <Option target="Release MSYS2W32" />
             <Option target="Debug MSYS2W64" />
             <Option target="Release MSYS2W64" />
             <Option target="Debug VS2022 X32" />
             <Option target="Release VS2022 X32" />
             <Option target="Debug VS2022 X64" />
             <Option target="Release VS2022 X64" />
             <Option target="Debug DMC" />
             <Option target="Release DMC" />
             <Option target="Debug lcc" />
             <Option target="Release lcc" />
             <Option target="Debug lcc64" />
             <Option target="Release lcc64" />
             <Option target="Debug BorlandC" />
             <Option target="Release BorlandC" />
             <Option target="Debug OW 32" />
             <Option target="Release OW 32" />
             <Option target="Debug OW 64" />
             <Option target="Release OW 64" />
             <Option target="Debug PELLES C" />
             <Option target="Release PELLES C" />
             <Option target="Debug PELLES C 64" />
             <Option target="Release PELLES C 64" />
             <Option target="Debug CLANG Mingw32" />
             <Option target="Release CLANG Mingw32" />
             <Option target="Debug CLANG Mingw64" />
             <Option target="Release CLANG Mingw64" />
             <Option target="Debug CLANG MSX32" />
             <Option target="Release CLANG MSX32" />
             <Option target="Debug CLANG MSX64" />
             <Option target="Release CLANG MSX64" />
             <Option target="Debug CLANG MSYS W32" />
             <Option target="Release CLANG MSYS W32" />
             <Option target="Debug CLANG MSYS W64" />
             <Option target="Release CLANG MSYS W64" />
             <Option target="Debug MSYS2 UCRT64" />
             <Option target="Release MSYS2 UCRT64" />
             <Option target="Debug Intel X32" />
             <Option target="Release Intel X32" />
             <Option target="Debug Intel X64" />
             <Option target="Release Intel X64" />
          </Unit>
          <Unit filename="src/logger.h">
             <Option target="Debug Mingw32 official" />
             <Option target="Release Mingw32 official" />
             <Option target="Debug Mingw64 CB" />
             <Option target="Release Mingw64 CB" />
             <Option target="Debug Mingw64 Dev-Cpp" />
             <Option target="Release Mingw64 Dev-Cpp" />
             <Option target="Debug CYGWIN 32" />
             <Option target="Release CYGWIN 32" />
             <Option target="Debug CYGWIN 64" />
             <Option target="Release CYGWIN 64" />
             <Option target="Debug CYGWIN N64" />
             <Option target="Release CYGWIN N64" />
             <Option target="Debug Mingw32 wl" />
             <Option target="Release Mingw32 wl" />
             <Option target="Debug Mingw64 wl" />
             <Option target="Release Mingw64 wl" />
             <Option target="Debug TDM MinGW32" />
             <Option target="Release TDM MinGW32" />
             <Option target="Debug TDM MinGW64" />
             <Option target="Release TDM MinGW64" />
             <Option target="Debug MSYS2W32" />
             <Option target="Release MSYS2W32" />
             <Option target="Debug MSYS2W64" />
             <Option target="Release MSYS2W64" />
             <Option target="Debug VS2022 X32" />
             <Option target="Release VS2022 X32" />
             <Option target="Debug VS2022 X64" />
             <Option target="Release VS2022 X64" />
             <Option target="Debug DMC" />
             <Option target="Release DMC" />
             <Option target="Debug lcc" />
             <Option target="Release lcc" />
             <Option target="Debug lcc64" />
             <Option target="Release lcc64" />
             <Option target="Debug BorlandC" />
             <Option target="Release BorlandC" />
             <Option target="Debug OW 32" />
             <Option target="Release OW 32" />
             <Option target="Debug OW 64" />
             <Option target="Release OW 64" />
             <Option target="Debug PELLES C" />
             <Option target="Release PELLES C" />
             <Option target="Debug PELLES C 64" />
             <Option target="Release PELLES C 64" />
             <Option target="Debug CLANG Mingw32" />
             <Option target="Release CLANG Mingw32" />
             <Option target="Debug CLANG Mingw64" />
             <Option target="Release CLANG Mingw64" />
             <Option target="Debug CLANG MSX32" />
             <Option target="Release CLANG MSX32" />
             <Option target="Debug CLANG MSX64" />
             <Option target="Release CLANG MSX64" />
             <Option target="Debug CLANG MSYS W32" />
             <Option target="Release CLANG MSYS W32" />
             <Option target="Debug CLANG MSYS W64" />
             <Option target="Release CLANG MSYS W64" />
             <Option target="Debug MSYS2 UCRT64" />
             <Option target="Release MSYS2 UCRT64" />
             <Option target="Debug Intel X32" />
             <Option target="Release Intel X32" />
             <Option target="Debug Intel X64" />
             <Option target="Release Intel X64" />
          </Unit>
       
    I save this "project" CB file into notepad++.
       
    Into IDE, CB react to ask me if I want reload new project or not. I respond yes.

    And, after, new click on "Rebuild all", and "crash" in wxWidgets  ... with Alert Box described below.

    Windows IDE disappear (snif), with generation of RPT file (the same with precedent ...)

    Thank's.



    Offline mannisp

    • Single posting newcomer
    • *
    • Posts: 5
    Re: The 12 October 2024 build (13584) is out.
    « Reply #8 on: November 10, 2024, 01:12:12 pm »
    There's a problem with editor font: When I am using laptop with external monitor fonts are fine, but when I use laptop alone with its own display (2880x1800), fonts in editor are miniscule, and they cannot be adjusted from editor settings. Whatever I choose for the font size it is just miniscule and cannot be read. The only way to change it to be readable is to use ctrl+ to zoom. Also zoom from menu does not work, only ctrl+ works. But this has to be done for each file separately, and when I change to use external monitor, fonts become too large. This can be solved of course by deleting layout file and starting from default.
    I tried to delete all files below AppData/Roaming/Codeblocks so that it starts from default settings, but it did not change the behaviour with laptop's own display. The problem is not only because of the resolution 2880x1800: when I use external monitor then fonts are fine also in laptop's display.

    My setup:
    Samsung Book4 Ultra with Intel(R) Core(TM) Ultra 9 185H
    Windows 11 23H2

    Offline MehdiChinoune

    • Single posting newcomer
    • *
    • Posts: 7
    Re: The 12 October 2024 build (13584) is out.
    « Reply #9 on: November 10, 2024, 01:20:04 pm »
    There's a problem with editor font: When I am using laptop with external monitor fonts are fine, but when I use laptop alone with its own display (2880x1800), fonts in editor are miniscule, and they cannot be adjusted from editor settings. Whatever I choose for the font size it is just miniscule and cannot be read. The only way to change it to be readable is to use ctrl+ to zoom. Also zoom from menu does not work, only ctrl+ works. But this has to be done for each file separately, and when I change to use external monitor, fonts become too large. This can be solved of course by deleting layout file and starting from default.
    I tried to delete all files below AppData/Roaming/Codeblocks so that it starts from default settings, but it did not change the behaviour with laptop's own display. The problem is not only because of the resolution 2880x1800: when I use external monitor then fonts are fine also in laptop's display.

    My setup:
    Samsung Book4 Ultra with Intel(R) Core(TM) Ultra 9 185H
    Windows 11 23H2

    https://sourceforge.net/p/codeblocks/tickets/1483/

    Offline mannisp

    • Single posting newcomer
    • *
    • Posts: 5
    Re: The 12 October 2024 build (13584) is out.
    « Reply #10 on: November 10, 2024, 01:39:07 pm »
    https://sourceforge.net/p/codeblocks/tickets/1483/

    Ok, thanks, it solved the problem!

    However, I must ask, are you guys kidding?!? This ticket was marked as fixed, meaning that the user is assumed to somehow know to change a mystical parameter "Technology" from somewhere in settings to be able to use different displays  >:(

    Offline stahta01

    • Lives here!
    • ****
    • Posts: 7699
      • My Best Post
    Re: The 12 October 2024 build (13584) is out.
    « Reply #11 on: November 10, 2024, 02:14:55 pm »
    https://sourceforge.net/p/codeblocks/tickets/1483/

    Ok, thanks, it solved the problem!

    However, I must ask, are you guys kidding?!? This ticket was marked as fixed, meaning that the user is assumed to somehow know to change a mystical parameter "Technology" from somewhere in settings to be able to use different displays  >:(

    As long as fresh installs ** defaults the correct way and the FAQs are updated I consider fixed to be okay; but, I have no idea if either is true.
    ** Fresh installs means deleting the CB config data and re-installing CB

    Tim S.
    C Programmer working to learn more about C++ and Git.
    On Windows 7 64 bit and Windows 10 64 bit.
    --
    When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

    Offline mannisp

    • Single posting newcomer
    • *
    • Posts: 5
    Re: The 12 October 2024 build (13584) is out.
    « Reply #12 on: November 10, 2024, 07:31:18 pm »
    As long as fresh installs ** defaults the correct way and the FAQs are updated I consider fixed to be okay; but, I have no idea if either is true.
    ** Fresh installs means deleting the CB config data and re-installing CB

    It does NOT default the correct way!

    Also, it is not mentioned anywhere that is easily found by somebody who has not been spending half of his/her life hanging around this forum.
    Specifically, it is not in user guide nor FAQ (in Wiki).

    Offline stahta01

    • Lives here!
    • ****
    • Posts: 7699
      • My Best Post
    Re: The 12 October 2024 build (13584) is out.
    « Reply #13 on: November 10, 2024, 08:15:52 pm »
    As long as fresh installs ** defaults the correct way and the FAQs are updated I consider fixed to be okay; but, I have no idea if either is true.
    ** Fresh installs means deleting the CB config data and re-installing CB

    It does NOT default the correct way!

    Also, it is not mentioned anywhere that is easily found by somebody who has not been spending half of his/her life hanging around this forum.
    Specifically, it is not in user guide nor FAQ (in Wiki).

    Untested patch that might fix fresh install issue.
    Code
    Index: src/sdk/cbeditor.cpp
    ===================================================================
    --- src/sdk/cbeditor.cpp (revision 13584)
    +++ src/sdk/cbeditor.cpp (working copy)
    @@ -1441,7 +1441,7 @@
         if (!control)
             return;
     #if defined(__WXMSW__) && wxCHECK_VERSION(3, 1, 0)
    -    const int technology = config->ReadInt(wxT("/technology"), 0);
    +    const int technology = config->ReadInt(wxT("/technology"), 1);
         if (technology == 1)
             control->SetTechnology(wxSCI_TECHNOLOGY_DIRECTWRITE);
         else

    Took a lot longer than I would have guess to find the likely fix location.

    Feel free to use this patch without using my name.

    And, feel free to update the FAQs

    Tim S.
    C Programmer working to learn more about C++ and Git.
    On Windows 7 64 bit and Windows 10 64 bit.
    --
    When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org