On 8/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > On 8/30/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > > Lucas C. Villa Real wrote: > > > On 8/30/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > > >> The FFTW library is a little stupid, since it can be compiled with float > > >> (libfftw3f.a) or double (libfftw3f.a) precision, and also as static (.a) > > >> or shared (.so). The default is double and static, but some apps wants > > >> float, and I think I came across some app that wanted it shared but I'm > > >> not sure which one now... > > >> Anyhow, we need to be able to have both installed at the same time, so I > > >> suggest we call one FFTW and the other one FFTWf (with --enable-float > > >> config option). > > > > > > Can't we just tweak the configure file and let it ship/compile both by > > > default? Seems more reasonable to me. > > > > That would be the best, but I don't know how to do that kind of tricks > > with autotools (which is, I guess, compiling same files with different > > DEFINES). I guess the easiest way to solve it is having two wrapper .c > > files, one for double and one for float precision, and in them do the > > define and include the real .c file, but this should be done by FFTW and > > not by us. > > > > But if you find a way to solve it by tweaking their autotools files, or > > perhaps with a hackish recipe, please go ahead. :) > > I think the simplest way would be the recipe which just compiles FFTW > twice. I suggest a metarecipe FFTW which includes two recipes, > FFTW-double and FFTW-float. I don't know if any app *needs* FFTW to be > linked statically; I'm guessing just building both libraries as shared > would be okay (if there's no configure flag set to tell it to compile > both at once).
Yes, this seems to be good enough. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
