Hi Mats, thanks for reporting this. I used "run build" on origin/master and didn't hit build issue (my settings below). If after the build failed, you do "run build" again (don't switch to RELEASE build) and the build turns successful then it may be related to multi-threaded build. I understand that installing pywin32.exe may help (https://sourceforge.net/projects/pywin32/files/pywin32/Build%20220/, make sure to match the (x86 or amd64) of the Python install). Let us know how it goes. Thanks
E:\IoTivity.gerrit\iotivity>run build Starting IoTivity build with these options: TARGET_OS=windows TARGET_ARCH=amd64 SECURED=1 RELEASE=0 TEST=1 LOGGING=0 ROUTING=EP WITH_TCP=1 WITH_UPSTREAM_LIBCOAP=1 MULTIPLE_OWNER=1 MSVC_VERSION= THREAD_COUNT=12 scons VERBOSE=1 TARGET_OS=windows TARGET_ARCH=amd64 RELEASE=0 WITH_RA=0 TARGET_TRANSPORT=IP SECURED=1 WITH_TCP=1 BUILD_SAMPLE=ON LOGGI NG=0 TEST=1 RD_MODE=CLIENT,SERVER ROUTING=EP WITH_UPSTREAM_LIBCOAP=1 MULTIPLE_OWNER=1 -j 12 -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Friday, March 24, 2017 12:28 PM To: Nash, George <george.nash at intel.com>; Prathamesh Ranade <ranade.prathmesh at gmail.com>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] IoTvity build error On 03/24/2017 01:17 PM, Mats Wichmann wrote: > On 03/24/2017 01:02 PM, Mats Wichmann wrote: > >> >> I've done the following, and an >> (a) constructed a python virtual environment using 2.7 (my default >> python is 3.6 on this machine, but that won't work for scons) >> (b) launch the visual studio-aware version of a command shell >> ("VS2015 >> x86 x64 Cross Tools Command Prompt") >> (c) activate the virtualenv by going into the directory, then into >> the Scripts subdirectory and running "activate" >> (d) pip install scons >> >> now we have a command shell that knows where all the Microsoft tools >> are, knows the right version of Python, and has scons in it. >> >> "run build" is happy with this setup > > That said, it failed to build through. Is the Windows build currently > having some problems? Or is there one of those "everything doesn't > populate right first time" things going on? > > LINK : fatal error LNK1104: cannot open file > 'out\windows\amd64\debug\oc_logger.lib' > randomtest.cpp > scons: *** [out\windows\amd64\debug\resource\IPCA\src\ipca.dll] Error > 1104 > > > the ipca stuff just went in, afaik. sorry, more info... the default settings in run.bat are: TARGET_ARCH=amd64 TEST=1 LOGGING=0 RELEASE=0 WITH_TCP=1 SECURED=1 MULTIPLE_OWNER=1 ROUTING=EP WITH_UPSTREAM_LIBCOAP=1 BINDIR=debug RD_MODE=CLIENT,SERVER looks like it's not happy with the default to build debug mode; when I build RELEASE=1 (-release argument to the script) it goes all the way through without complaint, even running the unittests. _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7Cstjong%40exchange.microsoft.com%7C6a7a0495cb4b43fa226608d472ebd8ee%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636259804737889105&sdata=IWfMIRGeuLXokHTtXR%2Fd7tuvWKh%2Flozr5GMerNKcBoM%3D&reserved=0
