meta-openembedded/meta-oe
Yoann Congal bd6a43e5f1
catch2: enable native and nativesdk
Since commit de3c8d3ff2 ("cli11: Upgrade 2.3.2 -> 2.5.0 to allow CMake
4+ compatibility"), cli11 depends on catch2 and is native&nativesdk. So,
catch2 also need to be native&nativesdk.

Fixes these warnings from AB[0]:
WARNING: Nothing PROVIDES 'nativesdk-catch2' (but virtual:nativesdk:[...]/meta-openembedded/meta-oe/recipes-support/cli11/cli11_2.5.0.bb DEPENDS on or otherwise requires it). Close matches:
WARNING: Nothing PROVIDES 'catch2-native' (but virtual:native:[...]/meta-openembedded/meta-oe/recipes-support/cli11/cli11_2.5.0.bb DEPENDS on or otherwise requires it). Close matches:

[0]: https://autobuilder.yoctoproject.org/valkyrie/#/builders/82/builds/377/steps/12/logs/warnings

Cc: Alper Ak <alperyasinak1@gmail.com>
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-07-25 17:12:11 -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 thin-provisioning-tools: fix bindgen build error with clang on octeontx2 2025-07-24 08:40:45 -07:00
files
lib/oeqa/selftest/cases
licenses licenses: add licenses for ktx-software 2025-07-22 20:02:18 -07:00
recipes-benchmark libc-bench: Always use libgcc runtime with clang on x86 2025-07-20 21:21:32 -07:00
recipes-bsp fwupd: set vendor_ids_dir 2025-07-15 07:49:27 -07:00
recipes-connectivity hostapd: enable 802.11be, SAE-PK, OWE, SuiteB, ACS, and MBO support 2025-07-17 08:53:08 -07:00
recipes-core msr-tools: Delete recipe 2025-07-25 17:09:25 -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 msr-tools: Delete recipe 2025-07-25 17:09:25 -07:00
recipes-extended valkey: upgrade 8.1.1 -> 8.1.3 2025-07-21 10:10:46 -07:00
recipes-gnome meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-graphics ktx-software: Add recipe v4.4.0 2025-07-22 20:02:18 -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 uim: Upgrade to 1.9.6 2025-07-25 17:09:25 -07:00
recipes-test catch2: enable native and nativesdk 2025-07-25 17:12:11 -07:00
COPYING.MIT
README.md
SECURITY.md

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