News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

The 03 October 2020 build (12207) is out.

Started by killerbot, October 03, 2020, 09:34:55 AM

Previous topic - Next topic

killerbot

new PATCHED wx dll , please download these too and replace your old ones !!!

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/wxmsw31u_gcc_cb_wx313_2D_gcc810-mingw64-2.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 03 October 2020 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2020/CB_20201003_rev12207_win64.7z
  - Linux :
   none

The current SDK version is : 2.4.0

Resolved Fixed:


  • ToDo: Fix buffer overflows (ticket #1008)
  • UI: Fix incorrect editor context menu placement shown from the right editor control
  • compiler: Fix Intel compiler when creating static libraries (ticket #1017, thanks Sylvain Miossec)
  • compiler: Fix building static libs if the option "Force Use of forward slash as path separator" is on (ticket #1012, thanks Tim Stahlhut)
  • UI: Make the dialog for asking if debugging should continue even building failed more user friendly
  • UI: Make sure the StdButtonSizer controls where buttons are placed
  • CC: Fix adding parenthesis and doc window not popping up on windows (Ticket #1001, thanks Miguel Gimenez)

Regressions/Confirmed/Annoying/Common bugs:




LETARTARE

Quotenew PATCHED wx dll , please download these too and replace your old ones !!!
Do we also need to change 'wx-314' and how ?
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

oBFusCATed

(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!]

killerbot

for the moment we are still on a patched wx 3.1.3

killerbot

will try step -up to 3.1.4 and see which patches will still need to apply. Anyone already some experience with 3.1.4 ?

gd_on

I work with wxWidgets 3.1.4 (no special patches), inside C::B and for my own applications without any special problems.
gd_on
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).

Miguel Gimenez


killerbot

work with 3.1.4 : aka you use it for your own projects, or you also used it to build CB yourself with it ?

LETARTARE

Vista Business Pack2
1-  build wx-3.1.4 with gcc-8.1.0-dw
2-  build cb-12207 with gcc-8.1.0-dw and wx-3.1.4
All is correct

3- use of CB with projects: no anomaly to detect
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

gd_on

Quotework with 3.1.4 : aka you use it for your own projects, or you also used it to build CB yourself with it ?
To be more precise, I use wxWidgets 3.1.4 without any patches in my own project, but also to build C::B (see my signature).
For C::B, I have just added in C::B code, some time ago, 2 or 3 wxCHECK_VERSION(3, 1, 4) but I'm not sure they are all needed now.
gd_on
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).

Miguel Gimenez

I use wx3.1.4 without changes to compile C::B master, and I haven't found any problem or side effect in C::B.

gd_on

To complete your information, here is a patch file between my C::B version and the official svn 12207.
Some comments :
1) in main.cpp, there was a wxPaintEvent / ProcessEvent some time ago. It was replaced by Update some time ago (suggested by M.Gimenez if I remember well). As this original couple of instructions is no more in C::B code, the Update is probably not necessary now.
2) In wxsglcanvas.cpp and wxsglcanvas.h, I have added some instructions because I need to initiate and use in wxSmith some new graphic variables (mSampleBuffers and mSamples) in my own developments. These variables were introduced, I think, in wxWidgets 3.0. May be, there is an other way to do this, but I have not found an other way.
3) In global_uservars.xrc, I have commented some instructions, because I had some minor problems when C::B draw these controls, at least in my french C::B version. I don't remenmber, if it's wxWidgets 3.1.4 related, sorry.
4) in lexer_cpp.xml, this is clearly not related to wxWidgets 3.1.4. It simply adds the "rename" keyword to the cpp lexer. This was discussed some time ago in http://forums.next.codeblocks.org/index.php/topic,23736.0.html.
If this can help you ...
gd_on
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).

wtfisgoingoff

CRC failed in file name. The file is corrupt! 

\CB_20201003_rev12207_win64\wxled.dll   


Windows 10 x64


Xaviou

Hi
Quote from: Smilence on October 05, 2020, 04:26:13 AM
CRC failed in file name. The file is corrupt! 

\CB_20201003_rev12207_win64\wxled.dll   


Windows 10 x64


Confirmed.

Regards.
Xav'
My wxWidgets's stuff : [url="https://wxstuff.xaviou.fr/"]https://wxstuff.xaviou.fr/[/url]

ollydbg

Quote from: Smilence on October 05, 2020, 04:26:13 AM
CRC failed in file name. The file is corrupt! 

\CB_20201003_rev12207_win64\wxled.dll   


Windows 10 x64


I can also confirm this issue.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.