I?m just following up on this, as I?ve still haven?t been able to build this 
with 2017, despite the openiotivity blog post and the updated wiki.
I?ve found that if the PC _only_ has VS2017 installed it doesn?t work. If you 
have _both_ VS2015 and VS2017 installed, you can compile with VS2017 just fine, 
and all unit tests are passing.

To anyone who got Iotivity compiling with VS2017, did you also have VS2015 
installed side-by-side?


Thanks
/Morten

From: Dave Thaler<mailto:[email protected]>
Sent: Monday, April 10, 2017 12:57 PM
To: Morrow, Joseph L<mailto:joseph.l.morrow at intel.com>; Morten 
Nielsen<mailto:mn at iter.dk>; Mats Wichmann<mailto:mats at wichmann.us>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Cc: mashraf at asp-netconsulting.com<mailto:mashraf at asp-netconsulting.com>
Subject: RE: [dev] Visual Studio 2017

Thanks Ashraf and Joey.
I?ve updated the iotivity wiki page<https://wiki.iotivity.org/windows> with 
that information.

From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of Morrow, Joseph L
Sent: Friday, April 7, 2017 3:11 PM
To: Morten Nielsen <mn at iter.dk>; Mats Wichmann <mats at wichmann.us>; 
iotivity-dev at lists.iotivity.org
Cc: mashraf at asp-netconsulting.com
Subject: Re: [dev] Visual Studio 2017

I haven?t done it yet (I?m still using VS2015), but I see that Muhammad Ashraf 
(mashraf at asp-netconsulting.com<mailto:mashraf at asp-netconsulting.com>) 
owns this blog and posted this:

http://openiotivity.org/blog/?p=94<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fopeniotivity.org%2Fblog%2F%3Fp%3D94&data=02%7C01%7Cdthaler%40microsoft.com%7Ce20273e7d08844a7d70508d47e02f7f3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636271998613380768&sdata=uyIp2InL%2FWNYm6P2J9V3xyR4Fq%2F%2FuHaw5v%2B%2FWJN2ldI%3D&reserved=0>

Thanks,

Joey Morrow

From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at 
lists.iotivity.org> [mailto:[email protected]] On Behalf 
Of Morten Nielsen
Sent: Friday, April 7, 2017 2:58 PM
To: Mats Wichmann <mats at wichmann.us<mailto:mats at wichmann.us>>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Subject: Re: [dev] Visual Studio 2017

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:[email protected]>
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/20170505/12e80737/attachment.html>

Reply via email to