e71ef5a4a1
Added tag to SRC_URI. Release information [1]: 1.9.7: Bugfixes, build system cleanups What's Changed * Fixes PreventInSourceBuilds.cmake to work with add_subdirectory by @morbo84 in #1383 * json_value.cpp bug in the edges of uint/int by @YaalLek in #1519 * Release 1.9.6 and move versions to 1.9.7 by @baylesj in #1566 * Fixed work secure_allocator on old compiers by @TsynkPavel in #1478 * Fix flag -DJSONCPP_USE_SECURE_MEMORY:BOOL=TRUE by @tfc in #1567 * fix(build): remove check_required_components for meson build by @chenrui333 in #1570 * the cgi module was removed from Python3.13 by @a-detiste in #1578 * Fix name of static library when targeting MinGW. by @mmuetzel in #1579 * Fix comparison warnings caused by 54fc4e2 by @JensMertelmeyer in #1575 * Drop pre-C++11 alternatives by @BillyDonahue in #1593 * feat: support std::string_view in Value API by @evalon32 in #1584 * Added Value::findType with String key by @SwintonStreet in #1574 * Set up for Bazel module builds. by @bcsgh in #1597 * Add a BUILD.bazel file for //example. by @bcsgh in #1602 * Fix "include what you use" issue by @victorvianna in #1625 * Make the build configuration under Bazel more correct. by @bcsgh in #1600 * Add Bazel tests by @bcsgh in #1601 * Return false in Reader::readValue when stack limit is exceeded by @xuhdev in #1619 * Remove deprecated/removed clang-tidy key AnalyzeTemporaryDtors (#1614) by @bmagistro in #1615 * [docs] Consuming JSONCpp via Conan package manager by @uilianries in #1622 * Cleanup README.md, fix broken link. by @baylesj in #1633 * Add gcovr.cfg to fix CI coverage merge errors by @baylesj in #1635 * Remove build directory exclusion from gcovr config by @baylesj in #1640 * Add test for allowDroppedNullPlaceholders by @baylesj in #1648 * Prevent test colision when running in parallel via RESOURCE_LOCK by @marty1885 in #1637 * fixup project version updater by @baylesj in #1649 * Update README with project status and focus by @baylesj in #1639 * Adding a cmake option to exclude the jsoncpp files from install. by @nv-jdeligiannis in #1596 * Change stack depth limit to 256 by @baylesj in #1657 * Fix uninitialized CMake variable in version.in by @baylesj in #1658 * Fix CMake deprecation warning for compatibility with CMake < 3.10 by @baylesj in #1659 * Scope JSON_DLL_BUILD to shared lib target only by @baylesj in #1660 * Fix number parsing failing under non-C locales by @baylesj in #1662 * Reject unescaped control characters in JSON strings by @baylesj in #1663 * Fix MSAN issue in #1626 by @baylesj in #1654 * Fix string_view ABI mismatch between library and consumers by @baylesj in #1661 * Revert "Fix number parsing failing under non-C locales" by @baylesj in #1664 * Fix use-after-free in Reader::parse(std::istream&) by @baylesj in #1665 * Update bazel config for 9.x by @keith in #1655 [1] https://github.com/open-source-parsers/jsoncpp/releases/tag/1.9.7 Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.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