meta-openembedded/meta-oe
Moritz Haase a08eabb3b8
leveldb: Allow to build with CMake 4+
The component itself builds just fine with CMake 4, but the tests don't as they
rely on a bundled version of GTest that is six years old. Since upstream is
inactive, the simplest course of action is to apply the 'minimum policy version'
override (as implemented in CMake, it only affects the GTest submodule).

System GTest can not be used instead (easily), as among other things it requires
C++14 and the project uses C++11.

Signed-off-by: Moritz Haase <Moritz.Haase@bmw.de>
CC: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-07-15 07:49:27 -07:00
..
classes signing.bbclass: make PEM loading compatible with OpenSC 0.26.0 2025-07-02 09:48:26 -07:00
conf reproducibility: move known non-repro list to layer.conf 2025-06-20 10:34:11 -07:00
dynamic-layers taisei: Upgrade to 1.4.3 2025-07-12 13:50:00 -07:00
files static-passwd-meta-oe: add flatpak user 2025-04-19 14:36:07 -07:00
lib/oeqa/selftest/cases
licenses licenses/X11: remove license 2025-04-29 08:45:35 -07:00
recipes-benchmark meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-bsp fwupd: set vendor_ids_dir 2025-07-15 07:49:27 -07:00
recipes-connectivity gattlib: upgrade 0.2.0 -> 0.7.2 2025-07-15 00:25:30 -07:00
recipes-core opencl-icd-loader: allow to build with cmake 4 2025-07-10 10:46:23 -07:00
recipes-crypto cryptsetup: upgrade 2.7.5 -> 2.8.0 2025-07-07 10:00:53 -07:00
recipes-dbs leveldb: Allow to build with CMake 4+ 2025-07-15 07:49:27 -07:00
recipes-devtools libubox: Update to latest tip of trunk 2025-07-15 00:25:28 -07:00
recipes-extended openwsman: Upgrade to 2.8.1 release 2025-07-15 00:25:32 -07:00
recipes-gnome meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-graphics opengl-es-cts: Allow to build with CMake 4+ 2025-07-15 00:25:30 -07:00
recipes-kernel kernel-selftest: Fix PTP selftest compilation for kernel 6.7+ 2025-07-09 09:16:08 -07:00
recipes-multimedia wavpack: Upgrade 5.6.0 -> 5.8.1 to allow CMake 4+ compatibility 2025-07-09 09:16:06 -07:00
recipes-navigation proj: Upgrade to 9.6.2 release 2025-07-12 13:50:02 -07:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing gutenprint: fix a build race-condition 2025-07-04 09:42:10 -07:00
recipes-security meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-shells meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-support freerdp: Allow to build with CMake 4+ 2025-07-15 00:25:29 -07:00
recipes-test linux-serial-test: Bump SRCREV to allow CMake 4+ compatibility 2025-07-11 08:35:27 -07:00
COPYING.MIT
README.md README.md: Hint at "git request-pull" 2024-09-14 08:43:55 -07:00
SECURITY.md meta: Add SECURITY.md file to all layers 2024-11-23 09:00:14 -08:00

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