Which version of libcoap do we want to pursue? We have a forked copy in resource/csdk/connectivity/lib which is moderately old. It's named libcoap-4.1.1, but does not match the layout of the upstream 4.1.1 release bundle - headers have moved to an include/coap directory in ours, something which happened in a later revision upstream (but in that revision, other things moved as well that have not moved in ours). I presume we've maintained that to suit iotivity needs over time so it has patches in it?
There is also the option to use upstream libcoap, enabled by a command-line option; that invokes a script in extlibs which grabs libcoap and builds it. At the moment, the one it grabs is also a fork of upstream. The default state at the moment is the embedded one in resource/. Thus a static checker build uses it - and reports quite a few possible issues: there are nine distinct reports comprising 13 issues. As usual with static check results, until they are triaged/tuned, some will end up not being important enough to pursue, but there is some meat in there as well. Is it worth cleaning the old fork, or should we try to move closer to upstream and recheck whether the same issues are still present there? (not for 1.3.1 obviously). _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
