summaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-support/fftw
Commit message (Collapse)AuthorAgeFilesLines
* recipes: remove blacklisted recipesMartin Jansa2017-08-311-21/+0
| | | | | | | | * as PNBLACKLIST message says, these recipes are blacklisted for long time and nobody showed any interest to fix them * remove all unused .patch and .inc files as well Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: Add -D_GNU_SOURCE to CFLAGSKhem Raj2017-04-241-0/+2
| | | | | | Helps fix build on musl Signed-off-by: Khem Raj <raj.khem@gmail.com>
* recipes: add removal date to PNBLACKLIST messagesMartin Jansa2017-04-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | * based on discussion in pndeprecated thread: https://patchwork.openembedded.org/patch/137573/ update the messages to warn possible users that the recipe will be removed before the end of the next development cycle (before Yocto 2.4 is released). * updated with: sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs` * then noticed couple recipes being blacklisted only based on DISTRO_FEATURES, so removed those: meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb meta-oe/recipes-navigation/gypsy/gypsy.inc meta-oe/recipes-navigation/navit/navit.inc meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb * if it isn't fixed by this date, it's fair game to be removed whenever someone gets around to i Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: Update to 3.3.6 releaseKhem Raj2017-03-111-3/+5
| | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: work around segfault when checking for presence of ARM NEONAndreas Müller2017-01-102-1/+84
| | | | | | | | | | | | | | * Mixxx segfaulted during start. Remote debugging lead to function 'really_have_neon()'. * qtractor segfaulted when adding instruments as whysynth or hexter * seems autodetection fails in some other environments too [1]. * if TUNE_FEATURES contain 'neon' we can assume our machine supports NEON so we don't need runtime detection [1] https://github.com/FFTW/fftw3/issues/30 Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: update 3.3.4 -> 3.3.5Andreas Müller2017-01-101-2/+2
| | | | | Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: Remove the fftw-dev package dependency on non-existent fftw package.Philip Balister2016-11-231-0/+2
| | | | | | | | | The fftw-dev package RDEPENDS on the fftw package, but the package is not created. Remove the dependency on fftw so that images using fftw-dev will build. Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: fix native buildAndreas Müller2016-09-261-1/+4
| | | | | Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: fix reconfigure error introduced in previous patchAndreas Müller2016-09-261-0/+3
| | | | | | | | | | | config.status: executing libtool commands | mv: cannot move ‘<WORKDIR>/build’ to ‘<WORKDIR>/build-fftw/build’: Directory not empty | WARNING: <WORKDIR>/temp/run.do_configure.21632:1 exit 1 from 'mv <WORKDIR>/build <WORKDIR>/build-fftw' | ERROR: Function failed: do_configure (log file is located at <WORKDIR>/temp/log.do_configure.21632) Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: build all configurations by one recipeAndreas Müller2016-09-264-46/+61
| | | | | | | | | | | | * 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 <schnitzeltony@googlemail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* meta-oe: remove trailing spacesMartin Jansa2016-08-222-2/+2
| | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* meta-oe: use bb.utils.contains() instead of base_contains()Ross Burton2016-04-281-1/+1
| | | | | | | | base_contains() is a compatibility wrapper and may warn in the future, so replace all instances with bb.utils.contains(). Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Revert "gnome-terminal, system-tools-backends, slim, benchfft, syslog-ng: ↵Martin Jansa2015-10-131-0/+21
| | | | | | | | | | move to nonworking directories" * use PNBLACKLIST instead This reverts commit 92ea562bafda6b201fae91c2bc13a404da4d581c. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: s/PN/BPN/Yue Tao2014-11-071-2/+2
| | | | | | | | | | | | | | 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 <Yue.Tao@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: add virtual/fftw to PROVIDES and EXCLUDE_FROM_WORLDMartin Jansa2014-10-063-0/+8
| | | | | | | | | | | | | | | * 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 <Martin.Jansa@gmail.com>
* fftw: Build native version as wellKhem Raj2014-05-031-0/+2
| | | | | | | imagemagick-native needs it Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: Upgrade to v3.3.4Paul Barker2014-04-206-18/+18
| | | | | Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw: Refactor EXTRA_OECONFPaul Barker2014-04-204-8/+4
| | | | | | | | | 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 <paul@paulbarker.me.uk> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* recipes: Unify indentationMartin Jansa2013-04-152-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* gnome-terminal, system-tools-backends, slim, benchfft, syslog-ng: move to ↵Martin Jansa2013-02-011-19/+0
| | | | | | | | | nonworking directories * this set does not build with distroless qemuarm as reported in 'State of bitbake world' thread, nobody volunteered to fix them Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fftw : Update to version 3.3.3.Philip Balister2013-01-097-31822/+24
| | | | | | | | | | | | * Convert --enable-neon selection to use neon tune feature. * Drop neon patch since fftw now has direct neon support. * Remove SRC_URI from each bb file and use only SRC_URI from fftw.inc file. The old recipe selected neon for all armv7 machines, which was not entirely correct. Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* pixman,libav,libvpx,fftwf: bump PR after arm OVERRIDES changes in oe-coreMartin Jansa2011-12-161-1/+1
| | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Drop PRIORITY variablePaul Eggleton2011-07-142-2/+0
| | | | | | | | | | | | | | | | 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 <paul.eggleton@linux.intel.com>
* fftwf 3.2.2: add Vesperix NEON codeKoen Kooi2011-06-192-1/+31799
| | | | | | See http://www.vesperix.com/arm/fftw-arm/index.html for details Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
* fftw: fix license checksums and delete old versionsKoen Kooi2011-06-194-27/+3
| | | | Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
* move layer into meta-oe in preparation for future splitsKoen Kooi2011-03-178-0/+90
As per TSC decision Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>