I can build fine with VS2015 installed. In the interest of reducing disk space, I don?t install VS2015 any longer, and only install VS2017, but now I can?t build IoTivity any longer. So this isn?t really whether all my paths etc are set up right (they are ? or rather the definitely should be as my build script does that ? just updated for VS2017 instead).
/Morten From: Mats Wichmann<mailto:m...@wichmann.us> Sent: Friday, April 7, 2017 2:43 PM To: Morten Nielsen<mailto:mn at iter.dk>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Visual Studio 2017 On 04/07/2017 03:38 PM, Morten Nielsen wrote: > Has anyone successfully compiled IoTivity with VS2017 ? > I?m getting a ?cl not found? error (the error happens to be the same as I was > getting back when I tried to compile for Windows ARM using VS2015). > But cl compiler is accessible from the commandline. > > > /Morten worked with 2015. I guess it's not actually "with VS" when you do it from a command line. For me the easiest was to open the VS cmd window, and in that window make sure python works, and install scons using "pip install", because that way it knows about all the paths to all the components. My VS2015 install offers up "VS2015 x86 x64 Cross Tools Command Prompt" and "VS2015 x86 ARM Cross Tools Command Prompt". Does not VS2017 do the same? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170407/da03c4b6/attachment.html>
