3f468ccce0
Remove patch, the change is already in code. Changelog: https://github.com/PJK/libcbor/releases/tag/v0.13.0 Changed: - Fix small typo in release script - Fix failing 32 bit tests due to cmocka macro repeating stack pushes - Set cmake_minimum_required to 3.5 - Fix float_ctrl ctrl assertions failing in debug mode - Check in vscode setup - Add CBOR sequences example - Add riscv64 config to CircleCI - Add a test for malformed definite maps - Add [[nodiscard]] support and auto-update to C23 in cmake - Configure ctest on to export the test results to CircleCI - Revamp the introduction doc into a more useful crash course - Add OSX asan/lsan supression config - Add cbor_copy_definite - Improve handling and coverage reporting of exhaustive enum switches - Add references to readme - Update python deps and related docs - Link tutorial in readme (and fix embedded RST formatting) - Add a doc note on lto linking - Add a doc for the reference count in cbor_array_set(). - Add gh link to docs - Add #355 to changelog - Bump version to 0.13.0 Signed-off-by: Andrej Kozemcak <andrej.kozemcak@siemens.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.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
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