linux/meta-openembedded.git/meta-oe/recipes-multimedia/xpext, branch nanbield

*.patch: add Upstream-Status to all patches

2023-06-21T16:15:20+00:00

There is new patch-status QA check in oe-core: https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a This is temporary work around just to hide _many_ warnings from optional patch-status (if you add it to WARN_QA). This just added Upstream-Status: Pending everywhere without actually investigating what's the proper status. This is just to hide current QA warnings and to catch new .patch files being added without Upstream-Status, but the number of Pending patches is now terrible: 5 (26%) meta-xfce 6 (50%) meta-perl 15 (42%) meta-webserver 21 (36%) meta-gnome 25 (57%) meta-filesystems 26 (43%) meta-initramfs 45 (45%) meta-python 47 (55%) meta-multimedia 312 (63%) meta-networking 756 (61%) meta-oe Signed-off-by: Martin Jansa Signed-off-by: Khem Raj

Convert to new override syntax

2021-08-03T17:21:25+00:00

This is the result of automated script (0.9.1) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Martin Jansa

recipes: rename distro_features_check to features_check

2019-11-22T01:51:37+00:00

Avoid warning due to the class rename in OE-Core. Signed-off-by: Denys Dmytriyenko Signed-off-by: Khem Raj

xpext-dev: Remove RDEPEND on empty xpext package.

2016-09-15T08:22:45+00:00

If xpext is included in a build (ie via dependency on mpv) then builds of core-image-sato-sdk will fail with errors such as below. warning: Can't install mpv-dev-0.15.0-r0@i586: Can't install xpext-dev-1.0+5-r0@i586: no package provides xpext = 1.0+5-r0 Signed-off-by: Drew Moseley Signed-off-by: Martin Jansa

recipes: add x11 to required DISTRO_FEATURES

2015-02-12T18:33:24+00:00

Signed-off-by: Martin Jansa

meta-oe: use BPN in SRC_URI

2014-07-15T12:56:55+00:00

Fixed SRC_URI: * ${PN} -> ${BPN}, use ${BP} if it was ${PN}-${PV} * ${P} -> ${BP} Otherwise we would meet do_fetch errors when we do the multilib, native or nativesdk build. Signed-off-by: Robert Yang Signed-off-by: Martin Jansa

xpext: Drop uneeded custom do_configure to fix B!=S builds

2014-07-15T12:53:54+00:00

Signed-off-by: Richard Purdie Signed-off-by: Martin Jansa

xpext: fix build with B!=S

2014-06-21T11:06:14+00:00

Signed-off-by: Richard Purdie Signed-off-by: Martin Jansa

recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues

2014-02-23T22:20:02+00:00

Changes: - rename SUMMARY with length > 80 to DESCRIPTION - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR Signed-off-by: Matthieu Crapet Signed-off-by: Martin Jansa

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa Acked-by: Koen Kooi