aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-multimedia/libpostproc
AgeCommit message (Collapse)Author
2015-02-12libpostproc: drop, moved to oe-coreMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-08-10libpostproc: switch to lu-zero's for on github with 12 fixesMartin Jansa
* last commit on videolan.org is more than 1 year old, lu-zero's for has couple of fixes and also defines the version in the code, use that instead of 0.0.0" Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-07-21libpostproc: fix S!=B failureTim Orling
Implement khem's suggestion, ${S}/configure $(EXTRA_OECONF). NOTE: with or without autotools-brokensep, the following: | WARNING: QA Issue: ELF binary 'libpostproc.so.52.0.100' | has relocations in .text Signed-off-by: Tim Orling <TicoTimo@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-02-23recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issuesMatthieu CRAPET
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 <Matthieu.Crapet@ingenico.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-04-15recipes: Unify indentationMartin Jansa
* 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 <Martin.Jansa@gmail.com> Acked-by: Koen Kooi <koen@dominion.thruhere.net>
2013-01-18libpostproc: Remove -disable-yasm as this is a nonexistent flagAndrei Gherzan
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2012-10-10libpostproc: Add git versionOtavio Salvador
This has been split from libav code during development of 0.9 series. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>