Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

Error following the getting started tutorial #42

Closed
alexiordan opened this issue Oct 23, 2016 · 3 comments
Closed

Error following the getting started tutorial #42

alexiordan opened this issue Oct 23, 2016 · 3 comments

Comments

@alexiordan
Copy link

I'm having issues following the getting started tutorial

I have installed VisualStudio 2015 Update 3 (with Visual C++)
After I clone the repo at following path (c:\gitrepos) I run into following issues:

  1. Running build.cmd throws following error:
    C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Platform.targets(44,5): error MSB8020: The builds tools for v140 (Platform Toolset = 'v140') cannot be found. To build using the v140 build tools, either clic k the Project menu or right-click the solution, and then select "Update VC++ Projects...". Install v140 to build using the v140 build tools. [c:\gitrepos\azure-iot-gateway-sdk\build\ZERO_CHECK.vcxproj]
  2. If I modify the build.cmd so to add to msbuild the parameter /p:VisualStudioVersion=14.0 , I get for a lot or projects the following error:
    628>LINK : fatal error LNK1104: cannot open file 'Microsoft.VisualStudio.TestTools.CppUnitTestFramework.lib' [c:\gitrepos\azure-iot-gateway-sdk\build\deps\azure-c-shared-utility\testtools\umock_c\tests\umock_c_wout_init_ut\umock_c_wo ut_init_ut_dll.vcxproj]

Please help

@alexiordan
Copy link
Author

alexiordan commented Oct 23, 2016

2 is still an issue.

For the 1st one, the fix is setting the VisualStudioVersion Environment variable to 14.0
set VisualStudioVersion=14.0

@alexiordan
Copy link
Author

Fix for 2 also:
Set Environment variable VCInstallDir to VS2015's one
set vcinstalldir="C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\"

For both issues it is strange since I did not have another version of Visual Studio installed, but 2015.

However, not it build successfully with all the tests passed.

@alexiordan
Copy link
Author

After all It seems I was using the Visual Studio 2012 ARM Phone Tools Command Prompt instead of Developer Command Prompt for VS2015 .

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant