Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on June 04, 2023, 05:54:00 pm

Title: The 04 June 2023 build (13311) is out.
Post by: killerbot on June 04, 2023, 05:54:00 pm
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 (http://forums.codeblocks.org/index.php/topic,3232.0.html).

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:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 04 June 2023 build (13311) is out.
Post by: killerbot on June 04, 2023, 05:55:02 pm
compared to yesterdays nightly:
Title: Re: The 04 June 2023 build (13311) is out.
Post by: nenin on June 05, 2023, 07:58:14 am
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)
Thanks, it is big step forward! And "svn13311" looks beautiful.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Neo on June 05, 2023, 09:49:48 am
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.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: nenin on June 05, 2023, 01:13:52 pm
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
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

project actually is using "C:\mingw64\nixman13_1w32u"
Title: Re: The 04 June 2023 build (13311) is out.
Post by: flycat on June 06, 2023, 11:13:00 am
Every time I use File->New->Class , Then click Create , click "add to project" Yes, the program will not respond.
This problem has existed for many years, is it only I encountered?
20.03 Works fine
The system is Windows 10 22H2
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Miguel Gimenez on June 06, 2023, 11:27:52 am
This issue is described on ticket 1393 (https://sourceforge.net/p/codeblocks/tickets/1393/).
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Khram on June 06, 2023, 06:00:14 pm
Quite often it crashes and freezes if GCC-3.4.4 compiler errors occur
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Pecan on June 06, 2023, 06:45:31 pm
Quote from: Neo on June 05, 2023, 09:49:48 am
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.

You cannot mix a clang compiler with a clangd Mingw process or vice versa.
Both must be clang or Mingw.
Check your clangd setings at Settings>Editor>Clangd>C/C++Parser>SpecifyClangdExecutableToUse.

Also see the explanation at https://wiki.codeblocks.org/index.php/CB_Clangd_Client and seach for the keywords "Dont't mix".
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Neo on June 07, 2023, 05:22:54 pm
Quote from: Pecan on June 06, 2023, 06:45:31 pm
Quote from: Neo on June 05, 2023, 09:49:48 am
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.

You cannot mix a clang compiler with a clangd Mingw process or vice versa.
Both must be clang or Mingw.
Check your clangd setings at Settings>Editor>Clangd>C/C++Parser>SpecifyClangdExecutableToUse.

Also see the explanation at https://wiki.codeblocks.org/index.php/CB_Clangd_Client and seach for the keywords "Dont't mix".

I am not sure if I can understand what the wiki says. But the 'don't mix' rule is not always true.

clangd plugin:
C:\apps\gnu\winlibs\mingw32\bin\clangd.exe

I tried `C:\apps\gnu\MSYS64\mingw32` or `C:\apps\gnu\MSYS64\mingw64` and both work with clangd.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: cbuser1 on June 08, 2023, 05:58:51 pm
Quote from: flycat on June 06, 2023, 11:13:00 am
Every time I use File->New->Class , Then click Create , click "add to project" Yes, the program will not respond.
This problem has existed for many years, is it only I encountered?
20.03 Works fine
The system is Windows 10 22H2

I've had this issue as well on windows 7. Unfortunately I got busy and couldn't test thoroughly the nightlies to see which which was the last nightly without this problem. The last time I posted I was on nightly CB_20210709_rev12487_win64.7z which I have yet to see freeze.
But from the changelog it wasn't obvious what has changed exactly that would cause this issue  to occur in the nightly that came after that.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: UberNewb2 on June 09, 2023, 05:43:59 am
Between 13215 and 13311 a change was made in the shift tab behavior. It now moves left in the tabs of open files, instead of un-indenting one tab stop. I *really* miss that.

Title: Re: The 04 June 2023 build (13311) is out.
Post by: myztmy on June 09, 2023, 11:28:05 am
Quote from: killerbot on June 04, 2023, 05:54:00 pm

Resolved Fixed:
  • fixed compiler detection of MinGW as supplied by installer is not working

Regressions/Confirmed/Annoying/Common bugs:

Yes, it can detect compiler  in my  MinGW64  directory now , but the compiler is judged as "GNU GCC Compiler" ,  not exactly as "GNU GCC MinGW64 Compiler" . Although this may not be relevant, the compiler still works normally,  but I can't stand it, just because I'm am a perfectionist ,virgo.

P.S.  Now that  every  nightly builds  C::B needs the other two files of the corresponding version  to run,  and  most easiest way is to unzip both of them into the same directory where you unzipped the nightly  , why not pack them together into a file,
Let's download once and unzip once  instead of  download three times and unzip three times :(.

Regards

Title: Re: The 04 June 2023 build (13311) is out.
Post by: jeRRy on June 09, 2023, 12:05:27 pm
Quote from: UberNewb2 on June 09, 2023, 05:43:59 am
Between 13215 and 13311 a change was made in the shift tab behavior. It now moves left in the tabs of open files, instead of un-indenting one tab stop. I *really* miss that.

For Windows, you can try renaming (or deleting) the File "default.cbKeyBinder20.conf" in "C:\Users\username\AppData\Roaming\CodeBlocks".

That works for me.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: UberNewb2 on June 09, 2023, 04:45:11 pm
Quote from: jeRRy on June 09, 2023, 12:05:27 pm
Quote from: UberNewb2 on June 09, 2023, 05:43:59 am
Between 13215 and 13311 a change was made in the shift tab behavior. It now moves left in the tabs of open files, instead of un-indenting one tab stop. I *really* miss that.

For Windows, you can try renaming (or deleting) the File "default.cbKeyBinder20.conf" in "C:\Users\username\AppData\Roaming\CodeBlocks".

That works for me.
Ah thank you very much, that solved it. Closed CB, deleted the file, restarted, and it resumed the old behavior. You're awesome.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: MortenMacFly on June 10, 2023, 03:48:42 pm
We did compile this nightly version also into an installer and would love to get feedback if it works well or not.
You can find two versions here:
The first one is without a compiler, the second one it with a compiler (MinGW).
All required executables/libs etc are bundled.

Looking forward to hear from you!
Title: Re: The 04 June 2023 build (13311) is out.
Post by: MortenMacFly on June 10, 2023, 03:57:05 pm
Quote from: myztmy on June 09, 2023, 11:28:05 am
Yes, it can detect compiler  in my  MinGW64  directory now , but the compiler is judged as "GNU GCC Compiler" ,  not exactly as "GNU GCC MinGW64 Compiler" . Although this may not be relevant, the compiler still works normally,  but I can't stand it, just because I'm am a perfectionist ,virgo.
I understand what you say, but that is probably a bit nut-picking.

GCC is MinGW on Windows. Also, MinGW should also be detected just fine now.
The different names are more for convenience in case you want to setup projects that really need to differ between those compilers.
In fact, I would guess most people have the MinGW64 suite that is GCC and compiles for Win64 and Win32.

If you tell me a 100% save way to detect these different compilers correctly let me know. Oh - and don't forget: There are not only different flavours and versions but also different distributions. And some may name their folders and files differently.

Making it short: I don't really want to spend time into trying to improve the situation. But as usual: Patches are welcome! :-)
Title: Re: The 04 June 2023 build (13311) is out.
Post by: MortenMacFly on June 10, 2023, 04:40:29 pm
Quote from: cbuser1 on June 08, 2023, 05:58:51 pm
I've had this issue as well on windows 7.
Can you confirm that this does only happen when the code completion plugin is active? Meaning. If you disable he CC plugin does it work?
Title: Re: The 04 June 2023 build (13311) is out.
Post by: cbuser1 on June 10, 2023, 07:31:37 pm
Quote from: MortenMacFly on June 10, 2023, 04:40:29 pm
Quote from: cbuser1 on June 08, 2023, 05:58:51 pm
I've had this issue as well on windows 7.
Can you confirm that this does only happen when the code completion plugin is active? Meaning. If you disable he CC plugin does it work?

I think so. I no longer got messages from NativeParser::.
Is NativeParser related to code completion?

When code completion was enabled, cb would freeze and the last message shown is the following:

NativeParser::OnParserEnd: Project "NONE" parsing stage done!.

It doesn't show the line with the original project name as it does when it doesn't freeze.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Pecan on June 10, 2023, 08:14:33 pm
Quote from: MortenMacFly on June 10, 2023, 03:48:42 pm
We did compile this nightly version also into an installer and would love to get feedback if it works well or not.
You can find two versions here:
  • http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2023/CB_20230604_rev13311_win64.exe
  • http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2023/CB_20230604_rev13311_win64-MinGW.exe
The first one is without a compiler, the second one it with a compiler (MinGW).
All required executables/libs etc are bundled.

Looking forward to hear from you!

when I try to download the first url:
https://forums.codeblocks.org/index.php/topic,25410.msg173188.html#msg173188

I get the following response. What am I doing wrong?
I get the same response with the second url.
Edit: looks like the word "setup" is missing from the urls
Title: Re: The 04 June 2023 build (13311) is out.
Post by: killerbot on July 02, 2023, 07:57:29 am
testing the forum ....
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Grit Clef on July 26, 2023, 11:38:09 am
Hi,
      I've successfully built this nightly on my machine. A few days ago I created a wxWidgets Project, there was nothing wrong. But now I'm receiving a script error creating another one. The error message is "arith op + on between 'null' and 'instance' ". Can anyone give me a good way to solve it?
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Miguel Gimenez on July 26, 2023, 12:17:10 pm
Just to clarify, 13311 gives error but the one you were using previously did not. Which is the revision number of the previous one?.
Can you attach the failing script and the steps to reproduce?.

Title: Re: The 04 June 2023 build (13311) is out.
Post by: Grit Clef on July 27, 2023, 09:26:58 am
It's the most strange thing that the revision number of the nightly I previously used is 13311, too.
The steps to reproduce:
Create a new wxWidgets project, and select wxWidgets 3.2. Specify project name, and project directory. GUI Builder is wxSmith, and the app is frame based. Uncheck the Debug configuration, because I've not built it. Then, select use dll, monolithic library, enable Unicode, and empty project. Click Next. At this time, the error occurs.
The attached file contains script.

Edit:
For the compiler use LLVM Clang Compiler, this is the only difference than the previous.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Miguel Gimenez on July 27, 2023, 02:13:06 pm
Can you tell me where are the wxWidgets libraries for Clang? (For GCC they are in wxWidgets-3.2.x\lib\gcc_dll)

Thank you.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Grit Clef on July 27, 2023, 02:59:05 pm
You're welcome. In fact I'm not sure, too.
I don't use wxWidgets library compiled by Clang, it's actually compiled by GCC. Since Clang is compatible with GCC and I also want to try the Clang compiler, I created that project. I didn't expect to get an error.
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Miguel Gimenez on July 27, 2023, 04:37:50 pm
Fixed in r13320 (https://sourceforge.net/p/codeblocks/code/13320/), thank you.

You can just paste the modified file in (CBfolder)\share\CodeBlocks\templates\wizard\wxwidgets
Title: Re: The 04 June 2023 build (13311) is out.
Post by: Grit Clef on July 28, 2023, 09:24:01 am
OK. You're welcome.