mirror of
https://github.com/thead-yocto-mirror/meta-openembedded
synced 2026-09-19 05:31:56 +02:00
License-Update: copyright years updated Changelog: 2020-05-31 -- 0.9.4 * Fixed: testrunner: No longer crashes when compiled with NDEBUG (GitHub #67) * Fixed: CMake: Support GTest 1.8.0 (GitHub #68) Thanks to Ryan Schmidt for the related report! * Fixed: CMake: Use variable GTEST_INCLUDE_DIRS (with plural "S") rather than GTEST_INCLUDE_DIR (GitHub #79, #81) Thanks to Wouter Beek for the related report! * Improved: CMake: Send config summary to stdout, not stderr (GitHub #72) Thanks to Scott Donelan for the patch! * Improved: Make -DURIPARSER_BUILD_TESTS=OFF unlock compilation without a C++ compiler; thanks to Fabrice Fontaine for the patch! (GitHub #69) * Added: Functions to make UriUri[AW] instances independent of the original URI string (GitHub #77 and #78) New functions: uriMakeOwner[AW] uriMakeOwnerMm[AW] * Added: CMake option URIPARSER_ENABLE_INSTALL to toggle installation of files, defaults to "ON" (GitHub #74, #75) Thanks to Scott Donelan for the patch! * Soname: 1:26:0 Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io> 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 revision: HEAD 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 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/openembedded-core to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch <remote>' 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>