aboutsummaryrefslogtreecommitdiffstats
path: root/meta-multimedia/recipes-mkv
AgeCommit message (Collapse)Author
2013-08-22mkvtoolnix: inherit gettext and export RUBYLIBMartin Jansa
* fails to call msgfmt in do_compile: MSGFMT po/cs.po ERROR: Function failed: do_compile (see mkvtoolnix/5.9.0-r0/temp/log.do_compile.3794 for further information) * fails to find rubygems.rb: <internal:gem_prelude>:1:in `require': cannot load such file rubygems.rb (LoadError) 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-27mkvtoolnix: add 5.9.0Koen Kooi
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-01-27libmatroska: add 1.3.0Koen Kooi
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-01-27libebml: add 1.2.2Koen Kooi
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>