Windows clang -- proof-of-concept

[qurious-pixel]

Built with PRs from:

~~https://github.com/RPCS3/rpcs3/pull/17552~~ ~~https://github.com/RPCS3/rpcs3/pull/17401~~ ~~https://github.com/RPCS3/rpcs3/pull/17017~~

https://github.com/RPCS3/rpcs3/pull/17372

Todo: silence warning for:

• [x] asmjit [ -Wdeprecated-anon-enum-enum-conversion ]

• [x] yaml-cpp [ -Wignored-attributes ]

• [x] libusb [ -Wunused-value ]

• [x] cubeb [ -Wdeprecated-declarations ]

• [x] Remove workaround for AVX512 with Windows Clang-Cl

EDIT: With VCPKG cache, clang-cl build completes in ~14mins. Without cache, ~3 hours.

[hcorion]

Please write the script in shell script instead of Powershell.

[Megamouse]

Please write the script in shell script instead of Powershell.

There was a GitHub runner issue with the env if you use a shell script. That's why I wrote it in Powershell. I believe it was something with shell running in a separate instance

[hcorion]

All our other Windows builds use shell script, what makes this one not work? It makes it significantly more annoying to maintain if it's in a different language

[Megamouse]

All our other Windows builds use shell script, what makes this one not work? It makes it significantly more annoying to maintain if it's in a different language

I believe it's related to the bat file, which doesn't work with a shell script

[qurious-pixel]

I don't think this is ready to merge as-is, since I am not the author of the respective PR's, but wanted to get feedback/reviews to move the work forward.

[qurious-pixel]

Switched to vcpkg manifest mode to have greater control over packages and versions. Using NuGet package caching for greater reliability. Builds with full cache in ~11 mins. Needs Package read;write;delete permissions to make use of saving and recalling cached packages.

[fentbuscoding]

1 million dollars

[schm1dtmac]

@qurious-pixel Would it be fine if I (or you, if you'd prefer) pushed the homebrew ccache removal in a separate PR, to fix the macOS arm64 build issues ASAP?

[qurious-pixel]

@qurious-pixel Would it be fine if I (or you, if you'd prefer) pushed the homebrew ccache removal in a separate PR, to fix the macOS arm64 build issues ASAP?

Yes, I think that a separate PR is perfectly fine. 👍

[elad335]

Can you update what is remained?

[qurious-pixel]

Can you update what is remained?

Everything is working as tested. Would like some AVX-512 testers. Also, if the repo supported package caching, the build would finish in less than 15 mins.

Package: Read, Write, Delete (Admin)