Author Topic: wxWidgets 3.3.1 can only be used in the ucrt platform, not the mingw64 platform?  (Read 122 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6081
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Hi, when I looked at the packages of the msys2, here: https://packages.msys2.org/base/mingw-w64-wxwidgets3.3

I see it only has 3 platforms: ucrt, clang64, clangarm64.

While if you looked at the wxwidgets 3.2 ( https://packages.msys2.org/base/mingw-w64-wxwidgets3.2 ), I see extra platforms: mingw64.

Is it because that the 3.3.1 will support the dark mode, and the dark mode API are only supported by the ucrt library?

Thanks.

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.

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1757
I know that wx3.3.1 samples crash on exit if you use MinGW with MSVCRT, see this issue.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6081
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
I know that wx3.3.1 samples crash on exit if you use MinGW with MSVCRT, see this issue.

Thanks for the reply. I have seen your issue report before, but when I try to search the issue by your user name "Miguel Gimenez", I couldn't find it. Oh, I see your nickname in github is: "wh11204".

So, it crashed on 64bit Windows 7(Am I correct? I guess you are using 64bit Windows 7) with a 32bit compiler: i686-w64-mingw32, which is using MSVCRT library.

For me, I would still try to use a 64bit compiler which is MSVCRT library not UCRT, and I'd try on a 64bit Windows 10 PC first. Does anyone has tried this combination before?

 
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.