MAME moving to c++20

[Robbbert]

If you haven't already, read this: https://www.mamedev.org/?p=563

If TL/DR, basically Windows 10 and 11 are the only versions where it will work. I tried Windows 7: there's an entry point not found so cannot start.

Also, for the Unix folk, QT5 is gone, need to use QT6.

Minimum version of GCC is now 11, although they recommend Clang. I'm staying with GCC while it works.

I haven't built 32-bit for a long time but I've heard it will no longer compile.

No April release; May is expected to be the next one.

I suspect that it might be possible to fix the windows 7 issue; I have a theory but can't be bothered to try it out.

This also means that the next "official" releases of ARCADE64 and MAMEUI will also be restricted to Win10/11 64-bit.

If you guys want to see what works, grab the latest git and try building.

[Calamity]

I don't do any testing on Windows 7 myself, anyway I'm glad we got the emusync features ready for 286-287 because I suspect some folks will be tied to Windows 7 to avoid upgrading their cabinets.

Since Windows 11 is basically a no-go territory and will only get worse, GroovyMAME/Emudriver support will remain limited to Windows 10 as long as it's around.

Linux is the future-proof path.

[Robbbert]

I did try out the possibility of fixing the windows 7 problem and it turned out to be quite simple. So the solution exists should anyone be interested.

Due to m$ limitations I couldn't "upgrade" any of my numerous pc collection to Windows 11, therefore I have never tried it. I wasn't going to be forced to buy a new computer to satisfy the requirements of a large foreign corporation - at least not yet. Still using 7 for day-to-day tasks, and 10 for emulation.

I know nothing about Linux, hoping to stay away as long as possible.