News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

The 01 November 2019 build (11890) is out.

Started by killerbot, November 01, 2019, 06:49:48 PM

Previous topic - Next topic

killerbot


IMPORTANT : THIS BUILD USES WX 313 with 2D SUPPORT.




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 : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw31u_gcc_cb_wx311_2D_gcc810-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls8.1.0.7z


The 01 November 2019 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2019/CB_20191101_rev11890_win64.7z
  - Linux :
   none

The current SDK version is : 1.46.0

Resolved Fixed:


  • envvars: Crash when closing Environment settings dialog (ticket #877)
  • wxSmith: Fix wrong grouping of radio boxes in the wxSmith settings dialog (fix: #875 thanks Miguel Gimenez for patch)
  • wxSmith: Add wxDIRP_SMALL flag for wxDirPickerCtrl (fix #861. Thanks to Miguel Gimenez)
  • debugger: Fix regression when executing additional commands bef
  • debugger: Fix crash when trying to attach when there is no loaded project (ticket #879)
  • lexer: Add syntax highlighting for Nim (ticket #657, thanks Artem VL)
  • UI: Make Plugin manager to have resizeable plugin info control
  • compiler: Add an option to targets which allows the user to select the linker executable to be used for the target
  • sdk: Improve const correctness of code executed by CompilerCommandGenerator::GenerateCommandLine
  • sdk: Small optimizations in MacrosManager
  • compiler: Make the LinkerExecutableOption::AutoDetect work as advertised
  • scripting: Bind CompileOptionsBase SetLinkerExecutable and GetLinkerExecutable
  • SpellChecker: Fix wrong white space handling on windows by using the scintilla word finding functions
  • wxSmith: fix assertion because of missing default style for wxListView ( ticket #884, thanks Miguel Gimenez)
  • fixed warnings and freezes on Windows when running SpellChecker update batch file

Regressions/Confirmed/Annoying/Common bugs:




killerbot

in the meantime wx 3.1.3 is building and shortly a nightly based on that will come ....

killerbot


Khram

Great, thank you! I will learn a new version of an excellent program.   :)
C++ & Fortran in MinGW-GCC-4.3.3 & WinLibs-GCC-14.2 with CB-13596

BlueHazzard

QuoteWhen typing a new word, previous mistakes occur. The re-check the spelling of these errors are corrected.
Sorry, bu i do not understand this. Does it work or not? If not, can you give an exact description what does not work? If it works all is ok :)

Khram

Quote from: BlueHazzard on November 02, 2019, 11:51:17 PM
QuoteWhen typing a new word, previous mistakes occur. The re-check the spelling of these errors are corrected.
Sorry, bu i do not understand this. Does it work or not? If not, can you give an exact description what does not work? If it works all is ok :)

Ok, thanks. I repeat. While typing a new word - does not work, and after, or, when working with old ready-made text - everything is fine. The general conclusion to the second day - it is already possible to work with some difficulties ...
C++ & Fortran in MinGW-GCC-4.3.3 & WinLibs-GCC-14.2 with CB-13596

Frank_CB

Hello,

Have built wx313 libraries on a Windows 10 64-bit platform. Have installed nightly version 11890 using wx313. Have built Release and Debug versions of SVN 11901.

Have successfully compiled and executed wxWidgets samples Calendar and Splash with MSVS2019 Community,with both wx311 and wx313 (both inside and outside the IDE). I have successfully built and executed these samples with previous versions of C::B using the wx311 libraries. After apparently successfully building/rebuilding the samples with either the nightly version or the SVN versions of C::B, using the wx313 libraries, I'm now encountering error status -1073741819 failures when running from within C::B's IDE. No errors, nor any output, is shown when executing the samples outside of C::B's IDE.

Anyone else experiencing similar results or has any suggestions on how to fix the problem? It's not apparent to me whether this is wxWidget's or Code::Block's issue.

Regards

stahta01

#7
Frank_CB: -1073741819 = c0000005

QuoteException code c0000005 is the code for an access violation.

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

Frank_CB

@Stahta01:

Thanks for your response and comment.  My programming calculator verified your result.  It never dawned on me to change the error code to hexidecimal. Your reference to that value being equivalent to 'Access Violations' is good info. Is that information publicly available from Codeblocks, or is it your own?

Regards

stahta01

#9
Quote from: Frank_CB on November 16, 2019, 10:05:36 PM
@Stahta01:

Thanks for your response and comment.  My programming calculator verified your result.  It never dawned on me to change the error code to hexidecimal. Your reference to that value being equivalent to 'Access Violations' is good info. Is that information publicly available from Codeblocks, or is it your own?

Regards

I use the Windows built in Calc to change it to Hex and then I google the HEX value without any leading Fs.

Edit: I likely add error code to the hex value.

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

killerbot

new nightly coming this evening, would only do wx 3.1.3, did we encounter any serious issues with it ?

gd_on

For  me, no problems with wx313 (until now).
I have just a minor problem with svn number which is always 11918 thouh it should be 11922 this morning (even after deleting autorevision.h which force a rebuild).
Windows 11 64 bits (25H2), svn C::B (last version or almost!), wxWidgets 3.3.2, Msys2 Compilers 16.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

oBFusCATed

Try to run the bootstrap script. I think it regenerates the revision.m4 file which is used to setup the numbers. If this doesn't work try to delete the revision.m4 and re-run bootstrap again.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

gd_on

 :-[ which boostrap ? I'm on Windows. boostrap is for linux, no ?
Windows 11 64 bits (25H2), svn C::B (last version or almost!), wxWidgets 3.3.2, Msys2 Compilers 16.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

oBFusCATed

Yes, it is unix thing. Then I have no idea. You have to probably debug the autoversionning tool. It is not unheard of it being broken. ;)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]