License-Update: Update the LICENSE file from README.md to LICENSE Changelog: ========== - Floating-point conversion between half, single and double-precision for subnormal values and NaN payloads is completed. These are relatively obscure unused parts of IEEE754 floats. - QCBOREncode_GetErrorState() can now be called after QCBOREncode_Finish() and it will always return the correct error. - User-defined error codes are now supported. The error state can be set with the new function QCBORDecode_SetError(). - Fixed a rare condition where QCBORDecode_ VGetNext() would not set the Item.uDataType to QCBOR_TYPE_NONE on error. - Function naming changed to better avoid name collision. This includes internal functions. This is to compensate for C not having name spaces like C++. - Documentation correctly describes mixing of traversal cursor used by GetNext with fetch by label in entered maps - Some increase in test coverage - A bunch of "TODO:" items were addressed. Most result in no change to the code, just changes to documentation and test coverage. Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
layer maintainer: Khem Raj raj.khem@gmail.com