aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-support/mbuffer
Commit message (Collapse)AuthorAgeFilesLines
* mbuffer: Update to version 20140310 from 20091227Ash Charles2014-06-101-5/+7
| | | | | | | | | | The previous version of mbuffer could not be built out-of-tree and seems rather old [1]. [1] http://www.maier-komor.de/mbuffer.html Signed-off-by: Ash Charles <ashcharles@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* mbuffer: add PACKAGECONFIG for md5Martin Jansa2013-07-301-0/+3
| | | | | | | * openssl is autodetected from sysroot * add PACKAGECONFIG to make it deterministic Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* recipes: Unify indentationMartin Jansa2013-04-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* mbuffer: import from OE rev d4f0211e2078d5033ae0dee74664de5520d8392dMartin Jansa2011-05-301-0/+18
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>