Changes since 7.0.1: 459946d3 version 7.0.2 bump 8879dd5e two element id optimization (#2264) ecfc63b4 Committing clang-format changes e0d153e9 Enum search for when hashing fails (#2263) fc169a51 enum reflection documentation 3d8354a6 Committing clang-format changes f3fc73cc Allow to construct a glz::http_server instance using an asio::io_executor (#2258) 625b6ddd Update README.md 56d20086 Update README.md d3b51565 Update glaze_DISABLE_SIMD_WHEN_SUPPORTED documentation 77fb1384 Update README.md f17d17ca Committing clang-format changes 69eed8c2 YAML support (#2243) 5d652476 Update json-schema.md (#2254) 04883eb1 BEVE and CBOR std::expected support (#2253) 8555337e FEATURE: [json] Add special handling for std::expected<void,E> (#2251) ddea99c5 Simple float (#2248) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.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