User forums > Nightly builds

The 04 June 2023 build (13311) is out.

(1/6) > >>

killerbot:
We switched to gcc 13.1.0 (on 04 June 2023) --> download the new wx/mingw dll's see link below

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


The 04 June 2023 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2023/CB_20230604_rev13311_win64.7z
  - Linux :
   none

The current SDK version is : 2.24.0

Resolved Fixed:


* fixed compiler detection of MinGW as supplied by installer is not working
* make wxSmithDemo and wxSmithSTC compile on later wx versions
* allow to manage Globs also via pop-up menu in project explorer
Regressions/Confirmed/Annoying/Common bugs:

killerbot:
compared to yesterdays nightly:

* again new compiler, now again POSIX based
* download the supportive dll's  (wx and mingw)

nenin:

--- Quote from: killerbot on June 04, 2023, 05:55:02 pm ---compared to yesterdays nightly:

* again new compiler, now again POSIX based
* download the supportive dll's  (wx and mingw)
--- End quote ---
Thanks, it is big step forward! And "svn13311" looks beautiful.

Neo:
Maybe clangd plugin is broken; it reports unrealistic 'errors'. See attached screenshot.

EDIT:
It seems clangd plugin conflicts with MSYS2 clangd (mingw-w64-clang-i686-clang-tools-extra). I switched back to winlibs clangd and it works like before.

nenin:
I observed strange thing:
path in CB console when fresh built file is executed:

--- Code: ---Set variable: PATH=.;C:\mingw64\nixman13_1w32u\bin;C:\mingw64\nixman13_1w32u;C:\mingw64\nixman12_2w32u\bin;C:\mingw64\nixman12_2w32u;C:\ProgramData\Oracle\Java\javapath;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Program Files (x86)\Common Files\AspenTech Shared;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\CryptoTech\CryptoCard;C:\Program Files (x86)\CryptoTech\CryptoCard;C:\Program Files\Wolfram Research\WolframScript;C:\Users\*****\AppData\Local\Microsoft\WindowsApps;c:\mingw64\nixman12_2w32u\bin

--- End code ---
actual path, from cmd:

--- Code: ---PATH=C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Common Files\AspenTech Shared\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\CryptoTech\CryptoCard\;C:\Program Files (x86)\CryptoTech\CryptoCard\;C:\Program Files\Wolfram Research\WolframScript\;C:\Users\****\AppData\Local\Microsoft\WindowsApps;c:\mingw64\nixman12_2w32u\\bin
--- End code ---

project actually is using "C:\mingw64\nixman13_1w32u"

Navigation

[0] Message Index

[#] Next page