Hi Thiago, Thanks for that, that is at least one step forward for the released versions.
But somehow I do not "get it".. Currently IOTivity is already depended on a version of tinyCBOR, since that is part of the script that one has to download manually. So I guess this can be incorporated in to the github version as well. To my knowledge the host repo of the submodule determines the version of the submodule, hence that can be the verified version. If an new version comes along, then verification of that new version needs to be done before updating the host repo with the new version of the submodule. But maybe my understanding is incorrect... Kind Regards, Wouter -----Original Message----- From: Thiago Macieira [mailto:thiago.macie...@intel.com] Sent: 31 January 2018 15:14 To: Wouter van der Beek (wovander) <wovan...@cisco.com> Cc: iotivity-dev@lists.iotivity.org Subject: Re: [dev] TinyCBOR 0.5 release Hello Wouter We'll update the script in IoTivity's extlibs/tinycbor to point to the new release. It's not a submodule so that we have a chance to test before pulling the trigger and figure out there were any regressions (there were in 0.5- beta). But now that you mention this, we should consider including TinyCBOR into the IoTivity packages when we release. It won't happen for Git, but it should work for the release. On Wednesday, 31 January 2018 02:14:23 PST Wouter van der Beek (wovander) wrote: > Hi Thiago, > > Nice! > > Will this be github submodule in IOTivity, e.g. so that one does not > have to do an separate github pull to get this code? Currently this is > quite annoying to set up the IOTivity code base, one has to download > more than 1 repo seperatly.. There is also another library that you > have to pull down separately, which also can be an github submodule in > IOTivity. > > Kind Regards, > Wouter > > -----Original Message----- > From: iotivity-dev-boun...@lists.iotivity.org > [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Thiago > Macieira Sent: 30 January 2018 22:59 > To: iotivity-dev@lists.iotivity.org > Subject: [dev] TinyCBOR 0.5 release > > Release page: https://github.com/intel/tinycbor/releases/tag/v0.5.0 > Docs: https://intel.github.io/tinycbor/0.5/ > Downloads > - https://github.com/intel/tinycbor/archive/v0.5.0.zip > - https://github.com/intel/tinycbor/archive/v0.5.0.tar.gz > > ---- Release announcement --- > > TinyCBOR release 0.5.0 > > TinyCBOR 0.5 contains numerous fixes and new API compared to 0.4. The > main feature in this release is the CBOR Validation API, which can be > used to perform a deeper validation of the contents than the simple > syntax correctness that the main parser API provides. In particular, > the API can be used to confirm that a given CBOR data type was encoded > using either the Canonical Format (RFC 7049 section 3.9) and the Strict Mode > (section 3.10). > The API can also be used to confirm CBOR Text Strings carry > properly-encoded UTF-8 text, a verification that the main parser does > not perform. > > Starting in this release, the TINYCBOR_VERSION macro will be defined > to the current version number. > > This release also has the possibility of building TinyCBOR as a shared > library on Unix systems. It is automatically enabled on systems > detected to use the ELF executable format. To disable it, pass > BUILD_SHARED=0 to make; to enable it on other systems, pass > BUILD_SHARED=1. To disable the static library, pass BUILD_STATIC=0 to > make. Note that TinyCBOR does not guarantee binary compatibility across > releases. > > Other relevant changes include: > > - The list of known tags includes the tags used for CBOR Object Signing > and Encryption (COSE - RFC 8152). > - The functions taking FILE* are now conditional on a hosted C > environment. They are not declared for freestanding C environments. > > Note: the zero-copy string functions announced with the 0.5-beta1 > release have been removed for further development. A new zery-copy > string access API will be provided in the 0.6 release. > > The project maintainer would like to thank the following people for > contributing to this release: Bertrand Roussel George Nash Erich > Keane Fabrice Fontaine Vipul Rahane > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev@lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
