On Nov 19, 2016 4:29 PM, "Nivedita Singhvi" <niveditasinghvi at gmail.com> wrote: > > On 11/19/2016 12:56 PM, Kevin Kane via iotivity-dev wrote: >> >> This should have been fixed on 1.2-rel with the following change, to >> work with TinyCBOR v0.4: https://gerrit.iotivity.org/gerrit/#/c/14179/ > > > > How will they know? > > For anyone doing anything on top of iotivity, and who is not > simply a developer contributing _to_ iotivity, they will want to > pick up a known, stable release to base on. They will expect that > to build. They will not want to base on a random dev tree snapshot. > > In addition, most developers will not hunt through the bug lists > to see known bugs in a release before downloading and testing. At > best, they will read the release notes. > > Most of the individual developers and maintainers are very good > about helping to address issues when users run into them. But that's > not a very scalable process, especially not as the iotivity user > base grows, and pointing to fixes and workarounds in the dev trains > is only helpful up to a point. > > > I am imploring the iotivity community, please: > > * Keep in mind the user base (respect their time and effort) > > * Don't release with build failures > > * If for some reason after the fact a release tarball fails to build > (as happened with 1.1.1), pull the build or mitigate in some way: > > - document issues clearly on release notes page > - pull the broken build > - push out an updated point maintenance release with build fix > > > At this point, none of the existing releases of iotivity are usable > as-is, without (undocumented) workarounds and patches. I would hope > this is not the case going forward from 1.2.1 onwards. I am very > appreciative of the fact that the team is releasing 1.2.1 asap, but am > not sure they would have if std compliance wasn't broken as well. >
THANK YOU! at least I know I'm not alone. > > >> >> Are you up to date? >> >> >> >> If you?re working from an older point of the branch, you can get around >> this by going into extlibs\tinycbor\tinycbor and doing a ?git fetch && >> git checkout v0.3.2? to use the previous version of TinyCBOR. >> >> >> >> *From:*iotivity-dev-bounces at lists.iotivity.org >> [mailto:iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Gregg >> Reynolds >> *Sent:* Saturday, November 19, 2016 11:52 AM >> *To:* iotivity-dev <iotivity-dev at lists.iotivity.org> >> *Subject:* [dev] 1.2.0 build failure >> >> >> >> >> $ scons >> >> >> >> ... >> >> >> >> resource/csdk/security/src/aclresource.c: In function 'AclToCBORPayload': >> >> resource/csdk/security/src/aclresource.c:628:24: error: 'CborEncoder' >> has no member named 'ptr' >> >> *size = encoder.ptr - outPayload; >> >> ^ >> >> resource/csdk/security/src/aclresource.c:640:27: error: 'CborEncoder' >> has no member named 'ptr' >> >> cborLen += encoder.ptr - encoder.end; >> >> ^ >> >> scons: *** >> [out/linux/x86_64/release/resource/csdk/security/src/aclresource.o] Error 1 >> >> scons: building terminated because of errors. >> >> > > > thanks, > Nivedita > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161119/b70b6df8/attachment.html>
