A lot of Windows builds are failing with: 'coap_add_token_to_empty_message' undefined
Just want to let folks know what is going on, so you don't waste time chasing it. This comes from the use of changes to upstream-libcoap - the changes to do so are in 1.4-rel and master, but the CI environment does not always have the modified library code, thus the failure. This is a CI-only problem - if you do a local build you will either have it succeed, or be prompted to update your extlibs/libcoap, after which it will succeed. The CI builders use a kind of caching, however, that means they can end up with the checkout of extlibs/libcoap being out of date (I think this happens after a change which as not been rebased has gone through a rebuild). There's a fix pending (25703) which is in a changeset which flips all of the targets in master to use the upstream libcoap - a changeset which is not completing its builds because of issues with Tizen and Android. I can separate out the change to more aggressively check out to the needed tag in libcoap from 25703 if other people are running into problems with this. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9756): https://lists.iotivity.org/g/iotivity-dev/message/9756 Mute This Topic: https://lists.iotivity.org/mt/23165160/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
