Mirror of git.openembedded.org/meta-openembedded https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=morty 2014-07-15T12:56:55+00:00 2014-07-15T12:56:55+00:00 Robert Yang liezhi.yang@windriver.com 2014-07-03T02:25:58+00:00 urn:sha1:05de0ca43d325d32faa6067013cd7c596f2001bf 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 <liezhi.yang@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> 2013-04-15T14:23:17+00:00 Martin Jansa Martin.Jansa@gmail.com 2013-04-13T20:49:41+00:00 urn:sha1:a45830a39bb47a9eab27980d52966226c9504ea4 * 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> 2011-04-10T12:43:41+00:00 Martin Jansa Martin.Jansa@gmail.com 2011-04-10T11:24:47+00:00 urn:sha1:89500c583e0f1dc1b4ffdf72914e08e505e427e0 * tested on shr-lite-image for om-gta02 and nokia900 (with meta-shr layer)