revisiting a topic which never had an action decided...
Currently, there are three possible versions of coap libraries. Most iotivity builds use a forked copy which lives in resource/csdk/connectivity/lib/libcoap-4.1.1. This is the current default. If WITH_UPSTREAM_LIBCOAP is defined/nonzero, a build is instead done against a git tree pulled from github. At the moment, if run.bat is used to do a Windows build, WITH_UPSTREAM_LIBCOAP is set by default, though it can be disabled at build time. execept... use of the upstream libcoap is at the moment commented out in favor of another fork, Dave Thaler's, which adds the tag our build is currently keyed to work against, and presumably some code changes to go with that. Meanwhile, real upstream has moved on to add proper DTLS support, which I assume we'd want to make use of (unless it's somehow not in sync with our use of mbedtls - I have no idea about this). I would propose in iotivity project master branch we immediately switch to defaulting WITH_UPSTREAM_LIBCOAP to enabled, so all platforms build with this same version (this build was broken at least for Linux but has recently been fixed). We should then investigate moving forward to later versions of upstream well before the next iotivity release, so there's no last-minute compatibility excitement. Thoughts? _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
