Finally remove wxWidgets

[stenzek]

Description of Changes

A year later and a ton of work, wx is finally gone! Celebrations!

Obviously merging this has to wait until the debugger is also merged (and maybe guitars).

CI probably needs to have some GCC builds added for coverage.

Rationale behind Changes

Where do I begin....

Suggested Testing Steps

Make sure Qt didn't break.

[TheComputerGuy96]

Qt didn't break (I was able to launch and play a few games fine)

I had to re-add package mode though to make an Arch package 🐸

[F0bes]

You make Linux users (including me) look horrible. We are an open community, you are able to suggest ideas to us. Instead of passive aggressive remarks, why not make a contribution.

Edit: Looks like the original comment was edited, my response was a response to that.

[SupervisedThinking]

You make Linux users (including me) look horrible. We are an open community, you are able to suggest ideas to us. Instead of passive aggressive remarks, why not make a contribution.

Edit: Looks like the original comment was edited, my response was a response to that.

Well I've deleted the comment because it's a waste of time. I already asked for a sane Qt5 support for Linux users, like all other major emulators offer as Citra, Yuzu, RPCS3, Dolphin do or just keep wxWidgets - Cemu works just fine.
But nobody cares because Windows 10/11 is the focused platform. I even created a PR in the past to fix Linux builds because nobody cared to test the removal of crucial stuff. If you have a look at the wording then the statement is clear: get rid of wxWidgets at all costs, don't care about anything else. I'm pretty sure wxWidgets could stay at least for 2.0 as legacy build for compat but well... I guess I'm wrong. So go on, remove the stuff nobody needs for Windows 10 anymore and Celebrations and stuff.

[JordanTheToaster]

You make Linux users (including me) look horrible. We are an open community, you are able to suggest ideas to us. Instead of passive aggressive remarks, why not make a contribution.
Edit: Looks like the original comment was edited, my response was a response to that.

Well I've deleted the comment because it's a waste of time. I already asked for a sane Qt5 support for Linux users, like all other major emulators offer as Citra, Yuzu, RPCS3, Dolphin do or just keep wxWidgets - Cemu works just fine. But nobody cares because Windows 10/11 is the focused platform. I even created a PR in the past to fix Linux builds because nobody cared to test the removal of crucial stuff. If you have a look at the wording then the statement is clear: get rid of wxWidgets at all costs, don't care about anything else. I'm pretty sure wxWidgets could stay at least for 2.0 as legacy build for compat but well... I guess I'm wrong. So go on, remove the stuff nobody needs for Windows 10 anymore and Celebrations and stuff.

Continuing to be passive aggressive isn't helping convince anyone.

[RedDevilus]

You make Linux users (including me) look horrible. We are an open community, you are able to suggest ideas to us. Instead of passive aggressive remarks, why not make a contribution.
Edit: Looks like the original comment was edited, my response was a response to that.

Well I've deleted the comment because it's a waste of time. I already asked for a sane Qt5 support for Linux users, like all other major emulators offer as Citra, Yuzu, RPCS3, Dolphin do or just keep wxWidgets - Cemu works just fine. But nobody cares because Windows 10/11 is the focused platform. I even created a PR in the past to fix Linux builds because nobody cared to test the removal of crucial stuff. If you have a look at the wording then the statement is clear: get rid of wxWidgets at all costs, don't care about anything else. I'm pretty sure wxWidgets could stay at least for 2.0 as legacy build for compat but well... I guess I'm wrong. So go on, remove the stuff nobody needs for Windows 10 anymore and Celebrations and stuff.

WX has long survived its initial projections of survival, and if you dislike it just stick to the older builds. Just like older OS with outdated specs fit with outdated software. Keeping compatibility for everything alive would require postponing progress or adding hacks back in again. If you want to handle that aspect for us, go ahead.

But don't expect us to do it for you, unless you have some valid reasons for atleast 10% of PCSX2 users. Either way we are all volunteers so we don't have to do anything that users suggest, but doesn't mean we don't listen and think about how much ideas help PCSX2. Trying to maintain WX was a nightmare when I tried to improve upon the monstrosity, now I don't have to cringe looking at the Qt variant having cleaned up the old mess. WX also has higher input latencies when I compared it to Qt so yeah, it's not done out of spite against users and perhaps you are just used to it but this isn't Bethesda or other emulators.

I apologise if this isn't the response you wanted but you did make a previous GitHub issue that was rejected.

And the other emulators started at Qt 5 or below and needs to revise a ton of the old code to be compliant for 6. PCSX2 started afresh with Qt 6.X so it made sense at the time to not hack it in for Qt5.

[arcum42]

This line tells it to install PCSX2-linux.sh, but this PR also deletes that file.

[SupervisedThinking]

Since Qt6 is meant for Windows 10 it's used. That's it. If I point out at least to keep it for legacy purposes: won't do. The project literally merged commits hours ago for the WX build but well: won't do. As I said it's a waste of time.

[RedPanda4552]

This sounds more like a disorganized rant about Windows being the end of the world than anything about dependency management. Linux users have the AppImage to take care of all that for them. Packagers can use a Qt 6 package when it is made available to them by their distro's package maintainers. End of story. Locked.

[refractionpcsx2]

Also FYI, dolphin has moved to qt 6 and made win 10 1908 the minimum requirement. If you're comparing their previous release, ours also works down to Windows 7

Please don't come in here with your disingenuous arguments

[stenzek]

This is ridiculous that we have to lock PRs because some users get mad about our choices. Clearly you haven't worked with the PCSX2 code base - the wx frontend is riddled with bugs, race conditions, overengineering and is very difficult to work with. That's why I tossed it out and started fresh.

If you want to use wx, the code is there. You can fork and maintain it yourself. That's the beauty of open source. But don't expect the maintainers to do it for you, when it's actively preventing us from making improvements (e.g. I can't do combined audio+video dumping until wx is gone). Plus, it hasn't been at feature parity in some time.

[stenzek]

Note: I've included #6161 in here for now, so we don't need to resolve the conflicts later. After the debugger is merged, this is good to go.