On 12/05/2017 12:29 PM, Mats Wichmann wrote: > 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.
Just to revisit the original thread, this task is on hold. In order to build using upstream-libcoap, a git checkout is needed. That's fine for a developer station, you just do the checkout and restart. For the jenkins builders, which are noninteractive, they have to be provisioned with the stuff from git - this is the same as currently happens for mbedtls, etc. So to run a test-all-platforms build with this change, coordination with the jenkins provisioning step is needed. And I'm not getting any response at all on LF staff on how to do that on an experimental basis. Next step I guess is to file a ticket there to "make it so", that usually gets a response, but I try not to assign work there too much. _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
