No it doesn’t. I can write “cl.exe” at the command prompt and that works, but when I run the scons build right after, it tells me CL can’t be found.
If you have 2015 and 2017 installed side by side it does work (From my understanding, it really uses 2015 regardless of what path you set up – I’m guessing because the path in the registry is used). /Morten From: Thiago Macieira<mailto:[email protected]> Sent: Thursday, July 27, 2017 9:22 AM To: Morten Nielsen<mailto:[email protected]> Cc: Daniel Mihai (WINDOWS)<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Maria Koutli<mailto:[email protected]>; Pramod H G<mailto:[email protected]> Subject: Re: building IoTivity with VS 2017 On quinta-feira, 27 de julho de 2017 08:43:24 PDT Morten Nielsen wrote: > 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-stud > io-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. It doesn't work with the command prompt either? That is, if everything is prepared in the environment, cl.exe is in PATH, etc.? -- 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
