See what look like a ton of answers. Fail on warns was recent for Linux.
Windows stuff for that was several months ago and should be debugged. Windows
build uses "upstream libcoap though it is a fork too. We need everyone forward.
On November 22, 2017 3:22:19 AM MST, "Wouter van der Beek (wovander)"
<[email protected]> wrote:
>Hi
>
>I know that an action was done to fix warnings and flag them as
>issues..
>However this has an drawback that I can't compile the stack on windows:
>
>c:\users\wovander\documents\wouter\standard-orgs\oic\work\iotivity_code\iotivity
>\resource\csdk\connectivity\lib\libcoap-4.1.1\include\coap\option.h(132):
>error
>C2220: warning treated as error - no 'object' file generated
>c:\users\wovander\documents\wouter\standard-orgs\oic\work\iotivity_code\iotivity
>\resource\csdk\connectivity\lib\libcoap-4.1.1\include\coap\option.h(132):
>warnin
>g C4244: 'function': conversion from 'unsigned short' to 'uint8_t',
>possible los
>s of data
>c:\users\wovander\documents\wouter\standard-orgs\oic\work\iotivity_code\iotivity
>\resource\csdk\connectivity\lib\libcoap-4.1.1\include\coap\option.h(147):
>warnin
>g C4244: 'function': conversion from 'unsigned short' to 'uint8_t',
>possible los
>s of data
>c:\users\wovander\documents\wouter\standard-orgs\oic\work\iotivity_code\iotivity
>\resource\csdk\connectivity\lib\libcoap-4.1.1\include\coap\option.h(162):
>warnin
>g C4244: 'function': conversion from 'unsigned short' to 'uint8_t',
>possible los
>s of data
>c:\users\wovander\documents\wouter\standard-orgs\oic\work\iotivity_code\iotivity
>\resource\csdk\connectivity\lib\libcoap-4.1.1\include\coap\coap_time.h(184):
>war
>ning C4244: '=': conversion from 'double' to 'coap_tick_t', possible
>loss of dat
>a
>resource\csdk\connectivity\src\cablockwisetransfer.c(1910): warning
>C4244: 'func
>tion': conversion from 'uint16_t' to 'unsigned char', possible loss of
>data
>scons: ***
>[out\windows\win32\amd64\release\resource\csdk\connectivity\src\cablo
>ckwisetransfer.obj] Error 2
>scons: building terminated because of errors.
>
>Can this either be fixed or can I have an work around so that I can
>compile the stack on windows?
>
>Kind Regards,
>Wouter
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
