fftw recipes

fftw recipes

[Andreas Müller]

Hi,

is there a technical reason why we have multiple fftw recipes (fftw /
fftwl / fftwf)?

or

before I start: Any complaints/comments if I

* merge all fftw's into one recipe named fftw splitting in multiple
packages (fftw / fftwl / fftwf / fftwq?)
* replace virtual/fftw by fftw
* make oe-core's alsa-utils fftw PACKAGFCONFIG[fftw] depending in fftw

Feedback welcome

Andreas

Re: fftw recipes

[Koen Kooi]

Op 06-09-16 om 09:02 schreef Andreas Müller:
> Hi,
> 
> is there a technical reason why we have multiple fftw recipes (fftw /
> fftwl / fftwf)?

Yes, at the time of writing there was no easy way to generate the different
libraries using one recipe. Worse, the headers conflict, even in the current
situation :/

regards,

Koen


> 
> or
> 
> before I start: Any complaints/comments if I
> 
> * merge all fftw's into one recipe named fftw splitting in multiple
> packages (fftw / fftwl / fftwf / fftwq?)
> * replace virtual/fftw by fftw
> * make oe-core's alsa-utils fftw PACKAGFCONFIG[fftw] depending in fftw
> 
> Feedback welcome
> 
> Andreas
> 

Re: fftw recipes

[Jack Mitchell]

On 06/09/16 08:02, Andreas Müller wrote:
> Hi,
>
> is there a technical reason why we have multiple fftw recipes (fftw /
> fftwl / fftwf)?
>
> or
>
> before I start: Any complaints/comments if I
>
> * merge all fftw's into one recipe named fftw splitting in multiple
> packages (fftw / fftwl / fftwf / fftwq?)
> * replace virtual/fftw by fftw
> * make oe-core's alsa-utils fftw PACKAGFCONFIG[fftw] depending in fftw
>
> Feedback welcome
>
> Andreas
>

I was looking at doing this myself. The library now has options to 
generate all three libs from a single source. However, the only way I 
could think to work with the header files was to have a fftw-headers 
which fftw/l/f all depended on so we don't get conflicting files in 
packaging.

Thanks for the heads up and I have no complaints as it saves me a job :)

Cheers,
Jack.