aboutsummaryrefslogtreecommitdiffstats
path: root/meta-initramfs/recipes-devtools/klibc/klibc_2.0.2.bb
AgeCommit message (Collapse)Author
2013-12-17klibc: upgrade from 2.0.2 to release 2.0.3Andrea Adami
Klibc now supports aarch64 / arm64 While there, remove PR/INC_PR from the recipes Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
2013-09-03klibc_2.0.2: refactor recipe to respect exec_prefixAndrea Adami
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
2013-06-18klibc: add SUMMARYAndrea Adami
Signed-off-by: Andrea Adami <andrea.adami@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>
2012-11-16klibc: upgrade from 2.0.1 to 2.0.2Andrea Adami
Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>