We don't control the code in the VSTSDK, so the best thing we can really do there is to just ignore the warnings.
It's not like this is a big deal anyway; Microsoft never really removes anything in practice. But even if they would do, we would notice due to build-errors. And then we could either apply a patch before we we compile, or inject some macros to remap the functions. But for now, let's keep this simple.
This seems to make the current CI run warning-free as of writing.
Due to touching the VSTSDK source-files, this PR conflicts with #32. It's easy to resolve, though, and either can easily be rebased on the other. Just worth noting ;)
We don't control the code in the VSTSDK, so the best thing we can really do there is to just ignore the warnings.
It's not like this is a big deal anyway; Microsoft never really removes anything in practice. But even if they would do, we would notice due to build-errors. And then we could either apply a patch before we we compile, or inject some macros to remap the functions. But for now, let's keep this simple.
This seems to make the current CI run warning-free as of writing.
Due to touching the VSTSDK source-files, this PR conflicts with #32. It's easy to resolve, though, and either can easily be rebased on the other. Just worth noting ;)