On Tuesday, 25 July 2017 02:37:09 PDT Pramod H G wrote:
> We did face similar issue using Visual Studio 2017 for windows.
> We could not resolve the issue by adding the cl.exe in PATH variable,
> Install or Uninstall of scons or python etc . Older Visual Studio 2013 or
> 2015 works fine and we reverted to that for building. There is some change
> in Visual Studio 2017 architecture and the path in which it puts the
> binaries and scons fully does not support that and hence the failure to
> detect Visual Studio 2017. Please refer to this link where there are
> changes being done to support Visual Studio 2017 in scons -
> https://bitbucket.org/scons/scons/pull-requests/. The patches there might
> help or we need to wait for Scons release 3.0 to fully support Visual
> Studio 2017.

The usual way of using the Microsoft compilers from the command-line is to 
launch the Commant Prompt link that it installs to your Start Menu.

If you have a different environment that you like (like a different terminal 
emulator), you should run the vcvarsall.bat file.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to