linux/meta-openembedded.git/meta-multimedia/recipes-multimedia/openal, branch thud-next

Make use of the new bb.utils.filter() function

2017-03-07T12:30:26+00:00

Signed-off-by: Peter Kjellerstedt Signed-off-by: Martin Jansa

meta-multimedia: use bb.utils.contains() instead of base_contains()

2016-04-28T08:38:39+00:00

base_contains() is a compatibility wrapper and may warn in the future, so replace all instances with bb.utils.contains(). Signed-off-by: Ross Burton Signed-off-by: Martin Jansa

openal-soft: disable examples, convert alsa and pulseaudio to PACKAGECONFIGs

2014-08-10T14:07:19+00:00

Signed-off-by: Martin Jansa

meta-multimedia: 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

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

openal-soft: initial add 1.15.1

2013-01-10T11:22:40+00:00