linux/poky.git/meta/conf, branch genericarm64

python3-meson-python: move from meta-python

2024-02-20T11:39:45+00:00

meson-python is a Python build backend built on top of the Meson build-system. It enables you to use Meson for your Python packages. https://meson-python.readthedocs.io/en/latest/ It is used as the PEP-517 build-backend for python3-numpy and python3-scipy. For other projects using the backend, see: https://meson-python.readthedocs.io/en/latest/projects-using-meson-python.html (From OE-Core rev: 57df1e3fd77a412fb7d585362a7263a4f847fe07) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

python3-pyproject-metadata: move from meta-python

2024-02-20T11:39:45+00:00

This is a dependency for python3-meson-python. (From OE-Core rev: b8c8d384b4622de7b5a4748e6e06665615674ba8) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

sanity.conf: Require bitbake 2.7.3

2024-02-19T11:58:12+00:00

Due to hashserv API changes in siggen, we need bitbake 2.7.3. (From OE-Core rev: 7172fd527fde440f26dd6cc371cde2720dbaa366) Signed-off-by: Richard Purdie

meta/conf/templates/default/conf-summary.txt: add a template summary

2024-02-19T11:47:53+00:00

Existing conf-notes.txt is not adequate in situations where the user needs to select a config template from several, or get an overview of them and is interested only in a brief explanation of what the template is for, but not extended multi-paragraph instructions for how to use it. Such summaries can be provided via conf-summary.txt and this patch adds such a summary for the oe-core default template. Updates to the tools and a tool for selecting templates which will make specific use of the summary will follow. (From OE-Core rev: aa96c2064a874714cfe4bac2fa622690e4c27ee4) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta/conf/templates/default/conf-notes.txt: remove

2024-02-16T23:17:13+00:00

This is present in the poky repository, even though it should not be: https://git.yoctoproject.org/poky/tree/meta/conf/templates/default I couldn't find which tool leaves the file in place when combining oe-core/bitbake/meta-yocto repos into poky, so this patch is rather a request to point me to where it happens (or just fix it directly there). Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

lib/oe/package: add LOCALE_PATHS to add define all locations for locales

2024-02-14T13:53:36+00:00

Some packages may contain localized files not located in default path ${datadir}/locale. Add the new variable LOCALE_PATHS to allow a recipe to define extra paths or even fully override the scanned directories. LOCALE_PATHS is set at ${datadir}/locale by default to keep the exact same behavior for the recipes which did not need modification. (From OE-Core rev: 0ffc7cf01225743789ac30dd325fca05b9203be1) Signed-off-by: Jonathan GUILLOT Signed-off-by: Richard Purdie

tcmode-default: Do not define LLVMVERSION

2024-02-13T13:51:41+00:00

There is a single version of llvm in core these days, furthermore the version is no longer asked for by recipes such as mesa, which would use llvm-config tool according to version of llvm found. (From OE-Core rev: 15d09b02b2632ab1cabc3b1bd9f521e6d3d3b83f) Signed-off-by: Khem Raj Cc: Ross Burton Acked-by: Martin Jansa Signed-off-by: Richard Purdie

feature-microblaze-versions.inc: python 3.12 regex

2024-02-13T13:51:41+00:00

Python 3 interprets string literals as Unicode strings, and therefore \s is treated as an escaped Unicode character which is not correct. Declaring the RegEx pattern as a raw string instead of unicode is required for Python 3. (From OE-Core rev: 662f52f1713c9f070550fc0c874eb62312218ea4) Signed-off-by: Adrian Freihofer feature-microblaze-versions.inc# Signed-off-by: Richard Purdie

python3-pyyaml: enable ptest

2024-02-10T14:13:24+00:00

Upstream is in the process of migrating testing to pytest, backport test_dump_load.py (the legacy_tests were throwing Errors and Failures). We don't really need to run upstream's test suite, but we do need to verify that our runtime is functional. https://github.com/yaml/pyyaml/commit/a98fd6088e81d7aca571220c966bbfe2ac43c335 (From OE-Core rev: b0fdf0688109ba6b87840a0837bebee3d9a27089) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

Revert "lzop: remove recipe from oe-core"

2024-02-09T16:18:05+00:00

This reverts commit dea5e8863792dc7bb3324b543e04da4c94a060aa. The original commit claims that lzop is unused in OE-core. That is not correct, the following places still use it and became unbuildable now: " meta/classes-recipe/image_types.bbclass:CONVERSION_CMD:lzo = "lzop -9 ${IMAGE_NAME}.${type}" meta/classes-recipe/image_types.bbclass:CONVERSION_DEPENDS_lzo = "lzop-native" meta/classes-recipe/kernel-uboot.bbclass: lzop -9 linux.bin meta/classes-recipe/kernel.bbclass:DEPENDS += "${@bb.utils.contains("INITRAMFS_FSTYPES", "cpio.lzo", "lzop-native", "", d)}" meta/classes-recipe/kernel.bbclass: lzop -df ${B}/usr/${INITRAMFS_IMAGE_NAME}.$img " Furthermore, LZO is the best compromise between kernel decompression time and size on low end ARM systems, that is why it is often used with e.g.: FIT_KERNEL_COMP_ALG = "lzo" FIT_KERNEL_COMP_ALG_EXTENSION = ".lzo" Reinstate the package to avoid breaking this use case. [RP: For me, the real reason to justify this is fact that several SoC/BSP layers do want this as a dependency] (From OE-Core rev: 6e8a0d66e05387d55c49a275faa7f4aa2bf6f2ac) Signed-off-by: Marek Vasut Signed-off-by: Richard Purdie