Files
meta-openembedded/meta-oe
Markus Volk 922ca44f5e rtkit: update 0.13 -> 0.14
- add HOMEPAGE
- update SRC_URI

Release notes

    Fix a bug that caused all RT privileges to sometimes be dropped on resume from suspend (#13 (closed))
    Drop autotools build system
    Add an rtkit_make_realtime_simple() with no arguments
    Drop default log level to reduce log spam
    Rename priority parameter of MakeThreadHighPriority to nice_level (does not change API)
    Implement org.freedesktop.DBus.Properties.GetAll
    Add a sysusers config
    Correctly specify client license as MIT
    A number of documentation and build cleanups

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-12-26 17:36:58 -08:00
..
2025-12-24 13:19:13 -08:00
2025-12-03 17:39:27 -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