On 07/27/2017 10:35 AM, Morten Nielsen wrote: > 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
right, scons has its own built-in algorithm for finding out where the compiler is, irrespective of %PATH%. As usually happens when one digs around and finds something internal and uses it, that broke eventually. > From: Thiago Macieira<mailto:[email protected]> > Sent: Thursday, July 27, 2017 9:22 AM > 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
