Feature/support non standard vcpkg configs

[vimanyu]

• Support configurations that do not ship with vcpkg by creating custom files on the fly and using those in the build process.
• Handle x86 on Windows (by appending -A Win32 to cmake configure)
• New flag "--crt_linkage" in build_desktop.py that sets the runtime linkage in MSVC (Windows only) for libraries built with vcpkg

 # /MD --crt_linkage dynamic # /MT --crt_linkage static 

Context:
vcpkg ships with default configurations for different platforms,
eg: x64-linux, x64-osx, x64-windows, x64-windows-static

Each of these configurations is a file containing various options (example: contents of x64-linux.cmake),

set(VCPKG_TARGET_ARCHITECTURE x64) set(VCPKG_CRT_LINKAGE dynamic) set(VCPKG_LIBRARY_LINKAGE static) set(VCPKG_CMAKE_SYSTEM_NAME Linux) 

We can provide custom configuration files to the vcpkg and leverage these new files in our build process.

[DellaBitta]

Adding a comment but leaving the previous review as the gating approval.

[anonymous-akorn]

Another thing to consider is how easy it will be to debug this if something goes wrong in this logic: it could cause an error far downstream (like a missing dependency), and might not be easy to figure out what went wrong or why.

Since the response files are small, I think it would be good to print their contents whenever modifying/generating one. e.g. in the logic to generate a response file out of an existing Linux response file, you could print both the Linux one used for the dependencies, and the new generated one. If nothing else, it'll help as a sanity check when going through CI logs.