meta-openembedded/meta-oe
Wang Mingyu 972faf66cf
aml: upgrade 0.3.0 -> 1.0.0
Changelog:
===========
- sys/queue.h: Remove "#include <sys/cdefs.h>"
- FUNDING.yml: Add github sponsors
- Stop single-shot also when no cb is set
- Replicate methods for every type
- Use explicit types in callbacks
- meson: Add run_command check argument
- meson: Relocate headers and pkgconfig
- kqueue: Call EV_SET without NOTE_ABSTIME on Mach
- kqueue: Pass unspecified timeout as NULL
- thread-pool: Make pthread_setcancelstate optional for Android
- build: Make librt optional
- Properly initialize global mutex

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-08-06 07:27:17 -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 spdm-utils: Move back to meta-oe 2025-08-01 17:23:41 -07:00
files static-passwd-meta-oe: add flatpak user 2025-04-19 14:36:07 -07:00
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 flashrom: upgrade 1.5.1 -> 1.6.0 2025-07-30 08:03:05 -07:00
recipes-connectivity gensio: upgrade 2.8.7 -> 2.8.15 2025-07-30 08:03:06 -07:00
recipes-core thin-provisioning-tools: Move out of clang dynamic layer to meta-oe 2025-08-01 17:23:41 -07:00
recipes-crypto cryptsetup: upgrade 2.7.5 -> 2.8.0 2025-07-07 10:00:53 -07:00
recipes-dbs leveldb: Fix cast warnings seen with clang-21 2025-07-29 12:22:21 -07:00
recipes-devtools spdm-utils: Add missing clang-native dependency 2025-08-05 12:17:55 -07:00
recipes-extended openwsman: Fix reprodubility issue due to abs paths 2025-08-04 11:45:26 -07:00
recipes-gnome meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-graphics aml: upgrade 0.3.0 -> 1.0.0 2025-08-06 07:27:17 -07:00
recipes-kernel ktls-utils: upgrade 1.0.0 -> 1.2.1 2025-07-30 08:03:06 -07:00
recipes-multimedia v4l-utils: Fix QA and build errors related to _TIME_BITS on 32-bit 2025-07-28 14:36:25 -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 usbguard: upgrade 1.1.3 -> 1.1.4 2025-07-30 16:40:03 -07:00
recipes-shells meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-support pv: upgrade 1.9.31 -> 1.9.34 2025-08-04 11:45:23 -07:00
recipes-test cpputest: update to latest revision 2025-07-28 14:36:25 -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