Perhaps this should be updated then: https://wiki.iotivity.org/windows
It suggests this: scons TARGET_OS=windows TARGET_ARCH=amd64 \ RELEASE=0 WITH_RA=0 TARGET_TRANSPORT=IP SECURED=1 WITH_TCP=0 \ BUILD_SAMPLE=ON LOGGING=OFF TEST=1 Even turning on WITH_TCP=1 same linker errors occur so there are more to it. It wasn?t until I used ?run build? things started building, but from why I can tell you can?t just build C-SDK with this script (copying the scons command that it ends up creating works for me however) /Morten From: Thiago Macieira<mailto:[email protected]> Sent: Monday, January 23, 2017 12:53 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>; Daniel Mihai<mailto:Daniel.Mihai at microsoft.com> Cc: Morten Nielsen<mailto:mn at iter.dk> Subject: Re: [dev] Windows build broken? On segunda-feira, 23 de janeiro de 2017 19:54:57 PST Daniel Mihai via iotivity-dev wrote: > Indeed, WITH_TCP=0 hasn?t been working anymore for Windows lately. I have a > patch to fix that, waiting to be merged, here: > > https://gerrit.iotivity.org/gerrit/#/c/16615/ Is it worth keeping the WITH_TCP=0 build working, for any system? Not including IoTivity Constrained, that's another story. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170123/2eeb96f9/attachment.html>
