seer VS mxe

CLion uses lldb.

I wrote https://github.com/daym/idea-native2-debugger as a stop-gap. It uses gdb and works in IntelliJ IDEA Community edition. Setting it up the first time is kinda weird since you need to add a new run/debug configuration "Native2Debugger". I could not figure out how to hook this directly into the existing run configuration that you use to run your program to begin with. Otherwise, I like how it turned out.

If you want a standalone frontend, https://github.com/epasveer/seer is extremely good.

And emacs has gdb integration. By now I tried it, and... I guess it's better than nothing.

(Shameless plug for my frontend to gdb --> https://github.com/epasveer/seer )

Cross compiler 64bit minGW along with MXE environment

I used to use MXE [1] to compile fully static Windows binaries on Linux VMs hosted with Travis. It needed to crane in everything though, so it was a source of bottlenecks from time to time. I was also uncertain about the provenance of a lot of the dependencies in that toolchain. So when Travis died I took the opportunity to move Windows builds back to gnu with msys2, all over GH Actions. These are actually comparatively snappy and I’m reasonably satisfied with it.

[1] https://mxe.cc/

MXE readily supports GCC 12 as a plugin (just a configuration line): https://github.com/mxe/mxe/tree/master/plugins/gcc12

Also, if you don't have any other significant dependencies, getting the development tools on Windows is not that hard with the Qt installer. Alternatively, there is MXE.

MXE (https://mxe.cc/) is a great cross compiler environment (on linux) that uses mingw.

You can install Docker to build on any Linux distro, and if one of those is Ubuntu then you can use https://github.com/mxe/mxe to further build for Windows. Or VirtualBox + Ubuntu + MXE.