meta-openembedded/meta-oe
Chen Qi acacb59a48
Revert "recipes: adapt to qemu.bbclass refactoring"
This reverts commit 24ff52ba3b.

The original patch was my bad. The patches for oe-core were re-worked,
but I forgot the recall this patch.

In fact, inheriting qemu is needed because it sets a clear barriar
for people to use qemu user mode. And the QEMU_OPTIONS settings
are also in qemu.bbclass.

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-05-29 22:28:02 -07:00
..
classes Revert "recipes: adapt to qemu.bbclass refactoring" 2025-05-29 22:28:02 -07:00
conf version-check.conf: mute version mismatch warning for dialog 2025-05-29 21:07:31 -07:00
dynamic-layers thingsboard-gateway: upgrade 3.7.2 -> 3.7.4 2025-05-21 07:38:27 -07:00
files static-passwd-meta-oe: add flatpak user 2025-04-19 14:36:07 -07:00
lib/oeqa/selftest/cases syzkaller: add recipe and selftest for syzkaller fuzzing 2022-10-21 09:57:59 -07:00
licenses licenses/X11: remove license 2025-04-29 08:45:35 -07:00
recipes-benchmark iperf3: enable native builds 2025-05-13 08:27:19 -07:00
recipes-bsp dediprog-flasher: enable native builds 2025-05-14 15:51:46 -07:00
recipes-connectivity iwd: update 3.6 -> 3.8 2025-05-22 08:13:04 -07:00
recipes-core uutils-coreutils: upgrade 0.0.30 -> 0.1.0 2025-05-27 10:33:01 -07:00
recipes-crypto libmcrypt: fix build with gcc-15.0.1 2025-04-01 20:43:27 -07:00
recipes-dbs postgresql: upgrade 17.4 -> 17.5 2025-05-21 07:38:25 -07:00
recipes-devtools Revert "recipes: adapt to qemu.bbclass refactoring" 2025-05-29 22:28:02 -07:00
recipes-extended Revert "recipes: adapt to qemu.bbclass refactoring" 2025-05-29 22:28:02 -07:00
recipes-gnome adw-gtk3: upgrade 5.8 -> 5.10 2025-04-23 19:35:02 -07:00
recipes-graphics Revert "recipes: adapt to qemu.bbclass refactoring" 2025-05-29 22:28:02 -07:00
recipes-kernel crash: fix reproducibility 2025-05-27 10:33:01 -07:00
recipes-multimedia libxmp: upgrade 4.6.2 -> 4.6.3 2025-05-21 07:38:24 -07:00
recipes-navigation gpsd: Add BUGTRACKER and HOMEPAGE 2025-04-30 09:17:37 -07:00
recipes-networking/cyrus-sasl cyrus-sasl: fix error with gcc-15 2025-04-19 14:36:04 -07:00
recipes-printing qpdf: upgrade 12.1.0 -> 12.2.0 2025-05-21 07:38:26 -07:00
recipes-security kernel-hardening-checker: Set recipe as machine specific 2025-05-22 17:39:10 -07:00
recipes-shells recipes: Fix variable assignment whitespace 2025-03-20 08:46:56 -07:00
recipes-support Revert "recipes: adapt to qemu.bbclass refactoring" 2025-05-29 22:28:02 -07:00
recipes-test catch2: upgrade 3.8.0 -> 3.8.1 2025-04-15 12:52:18 -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