Mirror of git.openembedded.org/meta-openembedded https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=hardknott-next 2018-09-19T03:17:02+00:00 2018-09-19T03:17:02+00:00 Hongxu Jia hongxu.jia@windriver.com 2018-09-17T16:05:24+00:00 urn:sha1:face5ee9c157c509ccbf35e2aa99aa272b860a05 Multiple -dbg packages per recipe is not encouraged, and only one is recommended and the code only works properly in some cases for one. Add RPROVIDES_${PN}-dbg to be compatiable with previous dbg packages requiring. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2014-05-05T16:31:29+00:00 Otavio Salvador otavio@ossystems.com.br 2014-05-05T15:26:18+00:00 urn:sha1:0502f9d575ddb0122bd10d325bd665a8964f5128 This fixes the Makefile so the client.txt file is copied from the original source tree. This fixes the out of tree build error. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> 2014-02-23T22:20:02+00:00 Matthieu CRAPET Matthieu.CRAPET@ingenico.com 2014-02-19T14:47:36+00:00 urn:sha1:c95e155780a0cf3a8fb59a2f86db6367d18116fc 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-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-08-29T07:02:13+00:00 Noor Ahsan noor_ahsan@mentor.com 2011-08-29T07:02:13+00:00 urn:sha1:0efa8c83632b62007db2a307b9264eb6bd0ac82f * Imported from oe.dev commit id d6f49fe115206047b41b0195724ba872897ef531 Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>