vcpkg

[DubbleClick]

I've switched most of my hobby projects over from pure cmake to cmake with the vcpkg integration. So far it has been a breeze.

I've had a look at it seems like most of our libraries could be built by vcpkg. This could potentially not only save us a lot of maintenance (vcpkg is very successful at guaranteeing build success) but also configuration.

This will take some research with linking against different libc/libc++'s though. Not a priority.

[DubbleClick]

https://github.com/gwdevhub/GWToolboxpp/pull/1257/files

Take a look at the amount of cmake configuration that just evaporated. Total vcpkg configuration is like 40 lines of code, 20 of which come from using a shared-library discord sdk in an otherwise static build.

[crazywhalecc]

It does look like a good approach. But it is different from our downloads and doctor at the moment, at least we separate downloading and building, and also this may require a huge PR or gradually replace the supporting libraries.

However, this is not our priority work, given that there are other issues to solve now. But I think windows should be a good start of this, because the default build components of many libraries on Windows do not support parallel builds. Also, I found vcpkg supports icu build, may be a good solution for #445 .

[DubbleClick]

I think vcpkg generally supports almost everything we need. The only thing I'm somewhat unsure about is its support to compile against different libc's.

[DubbleClick]

It supports it by specifying a cmake toolchain file to the triplet.