Author Topic: wxWidgets 3.1.7 is available  (Read 2718 times)

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 652
Re: wxWidgets 3.1.7 is available
« Reply #15 on: June 30, 2022, 12:18:28 pm »
Thanks.

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3255
Re: wxWidgets 3.1.7 is available
« Reply #16 on: June 30, 2022, 04:11:42 pm »
wxUSE_GRAPHICS_DIRECT2D and msys2 is still not working? Or at least i have to override the setup.h

Offline gd_on

  • Lives here!
  • ****
  • Posts: 732
Re: wxWidgets 3.1.7 is available
« Reply #17 on: June 30, 2022, 04:34:39 pm »
You still have to patch setup.h in \lib\gcc_dll\mswu\wx, line 1659 by :
Code
#define wxUSE_GRAPHICS_DIRECT2D 1   // Modif GD for CB >= 11701
Windows 10 64 bits (21H2), svn C::B (last version or almost!), wxWidgets 3.2.1, Msys2 Compilers 12.2.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 652
Re: wxWidgets 3.1.7 is available
« Reply #18 on: July 01, 2022, 07:50:55 am »
FYI: Updated wxWidgets on Mac using brew to 3.1.7 and successfully built and run C::B.

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1112
Re: wxWidgets 3.1.7 is available
« Reply #19 on: July 01, 2022, 12:00:46 pm »
There are some tickets related to Mac, can you reproduce any of them?

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 652
Re: wxWidgets 3.1.7 is available
« Reply #20 on: July 01, 2022, 03:00:40 pm »
Mac still has no debugging that is easy to do (or in my case get working), so first step to fix or investigate any Mac bugs is to get it so you get debug the code without resorting back to the god old printf days. So before I look at any Mac bugs I need to get debugging working first. IMHO and also Eran's Codelite changes for MAC is to add DAP debugger support. Eran has been working on the DAP library and integrating the changes into Codelite over the last few weeks. Some of the DAP library issues I have stumbled across have been fixed in DAP updates and some have been me or my config type issues.

Unfortunately based on past experience most of my large patches are not going to be accepted as they have or will be hijacked IMHO by someone who does not want to think or take the time to try to figure out why the patch is needed in the first place by the average user (not C::B devs) and as such I do not want to waste time on tickets and patches that go no where anymore. AS soon as I get the  "Please explain the reason for this patch..." I now give up as it's a waste of time responding as it goes no where.

Once I get DAP debugging working then I will supply info on the GIT repo and leave it for someone else to run with.