Propagate Visual Studio path into vcpkg.

By default vcpkg will pick whatever VS version it thinks is best, even
when running from inside a VS session, and mixing different versions of
the Clang toolchain seems to create weird issues.

Author: solemnwarning

msvc/vcpkg-deploy/vcpkg-deploy.vcxproj

@@ -63,7 +63,9 @@
       <GenerateDebugInformation>true</GenerateDebugInformation>
     </Link>
     <PreBuildEvent>
-      <Command>cd "$(SolutionDir)"
+      <Command>set VCPKG_VISUAL_STUDIO_PATH=$(VsInstallRoot)
+
+cd "$(SolutionDir)"
 "$(ProjectDir)install_vcpkg_dependencies.bat" x64-windows-static-v143 "$(TargetDir)"</Command>
     </PreBuildEvent>
   </ItemDefinitionGroup>
@@ -83,6 +85,7 @@
 set REHEX_WINSDK_INCLUDES=$(WindowsSDK_IncludePath)
 set REHEX_WINSDK_LIBDIRS=$(UniversalCRT_LibraryPath_x86)$(WindowsSDK_LibraryPath_x86)
 set VCPKG_KEEP_ENV_VARS=REHEX_SOLUTION_DIR;REHEX_WINSDK_INCLUDES;REHEX_WINSDK_LIBDIRS
+set VCPKG_VISUAL_STUDIO_PATH=$(VsInstallRoot)
 
 cd "$(SolutionDir)"
 "$(ProjectDir)install_vcpkg_dependencies.bat" x86-windows-static-enlyze "$(TargetDir)"