![]() We could do this by somehow executing this cmd from within the mki file "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -latest -property installationPath and then assigning the resulting value to the VS2017Dir variable: Unfortunately I am not familiar enough with the structure / syntax of make files so I just took the shortcut route and instead added the registry key, so that there was minimal mki file editing required. Ideally we would want to modify the mki file/s to use the vswhere.exe file instead of creating a new registry key to determine the VS install location. It is worth noting that I haven't tested this comprehensively yet to ensure that there are no unknown limitations, but it does appear to be working properly so I'd be curious to hear if anyone else has attempted something similar and if they are aware of any possible short-comings of this approach. As a side note I also updated these templates to work correctly with the selection filters in VS2019, if anyone wants these updated templates just let me know. ![]() In my case this was: " TOOL_VERSION = 14.29"Īfter doing all that my solution that I created using the VS2017 template file will build and execute correctly. Edit the " AssertToolSet.mki" file line 1063, changing from " 14.16" to the major version of the value we found in the above listed txt file.Open the file " C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\" to confirm the version number, in my case it was 3.(Obviously we need to modify the path if the install directory is different) Add registry value for VS2019 installation directory by creating a.so long story short I think I have found a solution to get bmake to work properly in VS2019 by doing the following (somewhat hack) solution: I was hoping to get started with C MDL development and didn't have the hard drive space or desire to uninstall my current devenv (VS2019 Pro) and then have to reinstall VS2017 along with all the same features / extensions.
0 Comments
Leave a Reply. |