meta-openembedded/meta-oe
Adam Duskett df2ac27812
kmscon: Add recipe
Provide sane defaults that do not have dependencies, such as
a dummy and terminal session support and basic fbdev support.

kmsconvt@.service must be added separatly or else
do_rootfs fails with the following error:

```
do_rootfs: Postinstall scriptlets of ['kmscon'] have failed. If the intention
is to defer them to first boot, then please place them into
pkg_postinst_ontarget:${PN} (). Deferring to first boot via 'exit 1' is no
longer supported.
```

Add a small patch to fix a compiling error when using LLVM as the
preferred toolchain.

Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2026-01-20 08:27:13 -08:00
..
classes meta-oe: image: optionally remove RAW image after sparse image creation 2025-09-15 09:55:16 -07:00
conf botan: Remove ptests execution on rv32 2025-12-31 08:28:50 -08:00
dynamic-layers rwmem: Fix tests to build with musl 2025-12-24 13:18:31 -08:00
files
lib/oeqa/selftest/cases
licenses licenses: add licenses for ktx-software 2025-07-22 20:02:18 -07:00
recipes-benchmark fio: ignore CVE-2025-10824 2025-12-16 19:57:32 -08:00
recipes-bsp acpitool: update SRC_URI 2026-01-12 13:20:11 -08:00
recipes-connectivity asyncmqtt: set CVE_PRODUCT 2026-01-12 10:25:56 -08:00
recipes-core recipes-core/toybox: Switch SRC_URI to HTTPS for reliable fetch 2026-01-02 22:30:11 -08:00
recipes-crypto libsodium: patch CVE-2025-69277 2026-01-12 10:25:55 -08:00
recipes-dbs lmdb: patch CVE-2026-22185 2026-01-12 10:25:58 -08:00
recipes-devtools grpc: Upgrade to 1.76.0 2026-01-14 16:59:47 -08:00
recipes-extended liblognorm: upgrade 2.0.8 -> 2.0.9 2026-01-20 08:27:11 -08:00
recipes-gnome gtkmm4: update 2025-12-03 17:39:27 -08:00
recipes-graphics kmscon: Add recipe 2026-01-20 08:27:13 -08:00
recipes-kernel libtracefs: upgrade 1.8.2 -> 1.8.3 2026-01-12 08:53:43 -08:00
recipes-multimedia libjxl: allow native build 2026-01-20 08:16:57 -08:00
recipes-navigation gpsd: upgrade 3.27.2 -> 3.27.3 2026-01-12 08:53:42 -08:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing qpdf: upgrade 12.2.0 -> 12.3.0 2026-01-13 08:29:02 -08:00
recipes-security bubblewrap: upgrade 0.10.0 -> 0.11.0 2025-12-28 08:14:40 -08:00
recipes-shells dash: upgrade 0.5.13 -> 0.5.13.1 2025-10-21 20:02:39 -07:00
recipes-support freerdp3: upgrade 3.20.0 -> 3.20.2 2026-01-20 08:27:12 -08:00
recipes-test cunit: inherit sourceforge-releases class 2025-11-12 09:38:58 -08:00
COPYING.MIT
README.md README.md: Change maintainer from Andreas to Khem for gnome, multimedia, xfce 2025-09-19 12:21:59 -07:00
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