chore: add xmake build support

[qudix]

Builds with msvc-cl, xmake does not currently support toolchain switching for packages on windows, so clang-cl is off the table for now.

How to build using xmake:

xmake build

This will fetch the project's package dependencies if they aren't already installed, and build all default targets. Packages aren't version pinned at the moment, this can be changed later if necessary.

As for options, there is one at the moment, sfse_xbyak which you can enable using:

xmake config --sfse_xbyak=true

If a VS project is desired, one can be generated for you:

xmake project -k vsxmake

The project kind vsxmake still uses xmake as the backend for building and such while allowing you to use the VS editor.

[gottyduke]

Thank you, this is great addition, msvc-cl is good enough. Currently the CommonLibSF doesn't honor SFSE_SUPPORT_XBYAK option anymore, it will always use that dependency and link it (I have checked most of the past CLib-related projects, none of them explicitly turned off that option).

Do you also plan on making an xmake plugin template after this? We can put all community template links on the README for people to choose from.

[qudix]

I don't think it's a good idea to remove that option because otherwise consumers will be saddled with another dependency they don't even use. Not all (xSE) plugins do hooking, even fewer of those use xbyak. I checked and all the other CommonLib's do default to OFF.

As for a plugin template, there needs to be a package for commonlibsf to pull from, which means making a custom xmake-repo registry.

[gottyduke]

Could you clarify the /utf-8 flag for me? I actually find another issue in xmake repo xmake-io/xmake-repo#2481 that's related to the fmtlib/fmt#3598

[qudix]

It sets the source (.cpp) and execution character set. I can add it if necessary. Did you run into an compilation error?

[gottyduke]

Did you run into an compilation error?

I did not have this error in xmake yet, but I did encounter the exact compilation error as fmtlib/fmt#3598 days ago in cmake-msvc setup, this was before I manually specified /utf-8 for all the projects, which has been working fine before the recent fmt 10.1 update.

I believe once fmt vcpkg port update their version to the latest with these PR fixes, this specific issue should not be present, but they haven't yet. Thank you for the fixes! Feel free to hit the merge button whenever your side of work is done and ready.

Edit for clarity:
I plan on adding the SFSE_SUPPORT_XBYAK option back, so nothing needs to change on your side.