linux/meta-openembedded.git/meta-oe/recipes-support/fftw/fftw.inc, branch gatesgarth-next

fftw: build all configurations by one recipe

2016-09-26T06:29:12+00:00

* avoids conflicts installing same files into sysroot * for packages requiring a specific version of fftw: simply add fftw to DEPENDS * no need for some distro decision - recipes depndong on fftw take what they need * each executable is packed into an own package to avoid dragging in all libraries Signed-off-by: Andreas Müller Signed-off-by: Martin Jansa

meta-oe: remove trailing spaces

2016-08-22T13:56:29+00:00

Signed-off-by: Martin Jansa

fftw: s/PN/BPN/

2014-11-07T14:05:05+00:00

Replace the PN with BPN to fix the multilib build. The error is: /ala-lpggp21/bpiolin/intel-x86-64-gplv2-4/bitbake_build/tmp/pkgdata/*/runtime-reverse/lib32-libfftw: No such file or directory Because the PN causes the package is named as lib32-liblib32-fftw. Signed-off-by: Yue Tao Signed-off-by: Jackie Huang Signed-off-by: Martin Jansa

fftw: add virtual/fftw to PROVIDES and EXCLUDE_FROM_WORLD

2014-10-05T23:07:53+00:00

* now when sysroot conflicts are fatal we really don't want to build multiple fftw providers in the same sysroot ERROR: The recipe fftwl is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemuarm/usr/include/fftw3.f Matched in manifest-qemuarm-fftw.populate_sysroot manifest-qemuarm-fftwf.populate_sysroot Signed-off-by: Martin Jansa

fftw: Refactor EXTRA_OECONF

2014-04-20T09:30:15+00:00

The configure flags common to all three fftw recipes are moved into fftw.inc and then each recipe just appends the extra flags it needs. This makes it easier to read and modify options which affect all three recipes. Signed-off-by: Paul Barker Signed-off-by: Martin Jansa

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* 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 Acked-by: Koen Kooi

Drop PRIORITY variable

2011-07-14T15:49:27+00:00

As discussed on the mailing list, this variable isn't useful and if wanted would be better implemented by distros using pn-X overrides. This patch executes: find . -regex ".*\.$bb\|inc$$" | xargs sed -i '/^PRIORITY = ".*"$/d' against the tree removing the references. Thanks to Phil Blundell for the command. (Prompted by oe-core rev: d122343362669c683acc4af295971a62cbc823fc) Signed-off-by: Paul Eggleton

fftw: fix license checksums and delete old versions

2011-06-19T18:41:25+00:00

Signed-off-by: Koen Kooi

move layer into meta-oe in preparation for future splits

2011-03-17T20:41:22+00:00

As per TSC decision Signed-off-by: Koen Kooi