meta-openembedded/meta-oe
Khem Raj bf090188e2
cppzmq: Use ALLOW_EMPTY
while ALLOW_EMPTY is frowned upon, this seems to be fitting to
solve the issue at hand here. When adding cppzmq to target SDK

This does not work resulting in

ERROR: Nothing RPROVIDES 'cppzmq' (but calc-server_latest.bb RDEPENDS on or otherwise requires it)

Adding cppzmq-dev dependency works for Target-SDK, but not for Target-Build:

ERROR: calc-server-latest-r0 do_package_qa: QA Issue: calc-server rdepends on cppzmq-dev [dev-deps]

Suggested-by: Lukas Weiß <lukas.weiss@janitza.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-03-17 22:24:37 -07:00
..
classes fitimage.bbclass: Add missing punctuation 2025-03-13 22:09:36 -07:00
conf reproducibility: Mark fsverity, libsdl2 packages as known non-reproducible 2025-03-15 23:05:32 -07:00
dynamic-layers packagegroup-meta-oe: move thin-provisioning-tools inclusion to clang dynamic layer 2025-03-13 09:50:13 -07:00
files libgpiod: Add gpio-manager/gpio to static IDs 2025-03-15 23:05:31 -07:00
lib/oeqa/selftest/cases
licenses openldap: make license match spdx identifier 2025-02-04 20:25:51 -08:00
recipes-benchmark fio: pass pkgconf args to configure script 2025-03-13 09:50:12 -07:00
recipes-bsp flashrom: Fix build with clang 2025-03-13 22:09:34 -07:00
recipes-connectivity cppzmq: Use ALLOW_EMPTY 2025-03-17 22:24:37 -07:00
recipes-core packagegroup-meta-oe: move thin-provisioning-tools inclusion to clang dynamic layer 2025-03-13 09:50:13 -07:00
recipes-crypto fsverity-utils: fix SRC_URI 2025-03-06 06:58:00 -08:00
recipes-dbs rocksdb: upgrade 9.0.0 -> 9.10.0 2025-03-11 19:35:32 -07:00
recipes-devtools php: upgrade from 8.2.26 to 8.4.4 2025-03-13 22:09:37 -07:00
recipes-extended minifi-cpp: Bump libfmt->11.1.4 and spdlog->1.15.1 2025-03-17 22:24:37 -07:00
recipes-gnome libjcat: upgrade 0.2.2 -> 0.2.3 2025-02-10 08:45:36 -08:00
recipes-graphics libsdl3: add fallback to console-build 2025-03-17 22:24:37 -07:00
recipes-kernel crash-cross-canadian: Update to match OE-Core virtual provider changes 2025-01-25 09:36:49 -08:00
recipes-multimedia faad2: upgrade 2.11.1 -> 2.11.2 2025-03-11 17:17:20 -07:00
recipes-navigation gpsd: condition the runtime dependence of pyserial on the pygps 2024-09-27 06:18:13 -07:00
recipes-networking/cyrus-sasl Drop unnecessary SRC_URI md5sum from the recipes in meta-oe. 2024-11-05 19:19:22 -08:00
recipes-printing qpdf: upgrade 11.9.1 -> 11.10.1 2025-02-26 08:30:55 -08:00
recipes-security usbguard: Patch for protobuf 30.0 API changes 2025-03-13 09:50:12 -07:00
recipes-shells zsh: modernise autoconf use 2025-02-27 20:28:17 +00:00
recipes-support procmail: Fix build with GCC-14 2025-03-16 14:24:21 -07:00
recipes-test catch2: upgrade 3.7.1 -> 3.8.0 2025-03-10 21:15:03 -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