That would be great, thanks for volunteering to clean this up! Dave
-----Original Message----- From: Mats Wichmann [mailto:[email protected]] Sent: Tuesday, December 5, 2017 11:29 AM To: Dave Thaler <[email protected]>; IoTivity Developer List <[email protected]> Subject: Re: [dev] which libcoap to use in master branch? On 12/05/2017 12:25 PM, Dave Thaler wrote: > resource/csdk/connectivity/lib/libcoap-4.1.1 > this one is obsolete and should have no new features added. It should > be deleted as soon as all builds pass with the newer libcoap. > That's always been the plan. > > My fork is the current working version and is what should be used > today > > The github libcoap is what we should try to use in the future, but > they didn't accept iotivity's libcoap changes and instead made non-compatible > changes so that it would require a bunch of iotivity work before we can > actually use it. For example, it has an RFC-compliant COAP-over-TCP > implementation > that differs from the one that iotivity uses. And iotivity just uses > libcoap to compose/parse packets, not for the business logic, which in my view > is bad. Iotivity should really be rewritten to be a clean layer on top of > the normal libcoap APIs. I don't expect that to happen any time soon though > as I've not heard anyone signing up for significant work. > > Dave Okay, thanks for the clarifications. I can submit a patch that defaults the other platforms to WITH_UPSTREAM_LIBCOAP and make sure my assertion that they'll build now is actually correct. _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
