There are already two different PRs to Scons that adds VS2017 support (none of them accepted yet): https://bitbucket.org/scons/scons/pull-requests/489/add-support-for-visual-studio-2017-using/diff (nice and simple) https://bitbucket.org/scons/scons/pull-requests/428/support-for-visual-studio-2017/diff (quite extensive)
The main problem is that up until VS2017, you used the registry to find the location of the compiler and Scons relies on that. Since VS2017 now supports side-be-side install for multiple different versions and editions of VS2017, that is no longer the case. I also see that this past week, Ibrahim Esmat is adding a bunch of UWP related stuff to both Iotivity and Scons. which makes me very happy. /Morten From: Daniel Mihai (WINDOWS) via iotivity-dev<mailto:[email protected]> Sent: Thursday, July 27, 2017 8:26 AM To: Thiago Macieira<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Maria Koutli<mailto:[email protected]>; Pramod H G<mailto:[email protected]> Subject: [dev] building IoTivity with VS 2017 I also experienced significant problems with SCons-based builds when I installed VS 2017, and I vaguely remember that it was hard for me to recover and go back to VS 2015. Since then: 1. I always use VS 2017 in a separate VM, not on the same machine where I use VS 2015. 2. One of my colleagues started looking into possibly adding support for VS 2017 into SCons. Let's hope that #2 will be successful. Otherwise, I'm afraid I don't have any great ideas regarding building IoTivity with VS 2017 at this point. Dan From: [email protected] <[email protected]> on behalf of Thiago Macieira <[email protected]> Sent: Tuesday, July 25, 2017 9:42 AM To: [email protected] Subject: Re: [dev] How to build native libraries for Iotivity in order to load them in Java 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbitbucket.org%2Fscons%2Fscons%2Fpull-requests%2F&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C35baa70cd9e2422bc4d508d4d37c29c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636365977619456871&sdata=7E5GlOkW9%2FRlO0L%2BTHrbjh5DgMaACCFaUmlsHRl3sm0%3D&reserved=0. > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C35baa70cd9e2422bc4d508d4d37c29c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636365977619456871&sdata=ydrVaEKcTF3F2rwuRftCzk9ADeWnT2vUAdideuD5I2o%3D&reserved=0
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
