Mirror of git.openembedded.org/meta-openembedded https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=walnascar 2014-12-19T19:13:12+00:00 2014-12-19T19:13:12+00:00 Philip Balister philip@balister.org 2014-12-18T18:40:45+00:00 urn:sha1:b1ffc521bd4f5dc62fd346fdc4abf4667a983934 The configure.py script now has support for cross compiling. This simplified the recipe substantially. The recipe was tested with gnuradio-companion on the zedboard and ettus-e300. This is the first time we have been able to use grc with pyqt built with OpenEmbedded. Build tested on armv7, x86, x86_64 and mips. Dropped patches from previous versions. Signed-off-by: Philip Balister <philip@balister.org> 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> 2013-01-02T08:08:49+00:00 Martin Jansa Martin.Jansa@gmail.com 2012-12-25T19:19:13+00:00 urn:sha1:0618ebdbecbe443ef35c7cf943b979625497fd8e Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>