[SciPy-user] disabling fftw3 during scipy build

[Barry Wark]

Thanks for the info. I've built a couple eggs for OS X 10.5
(Universal) from SVN trunk. Neither include fftw3.

One is statically linked to libgfortran (using setupegg.py bdist_ext
-L <path_to_copy_of_libgfortran.a>), one dynamic.

Both are available at
http://rieke-server.physiol.washington.edu/~barry/python/ (you'll have
to download them via a browser instead of easy_install -f since both
eggs are in the same folder). I would appreciate if some folks could
give them a test. If things look kosher, I'll build eggs for the
latest stable and for trunk.

Barry

On Thu, Feb 14, 2008 at 4:12 AM, David Cournapeau
<david at ar.media.kyoto-u.ac.jp> wrote:
>
> Barry Wark wrote:
>  > Hi all,
>  >
>  > I would be happy to start producing OS X eggs of scipy for
>  > distribution. At our site, we build scipy with fftw3 from MacPorts. I
>  > know the preference is to build eggs for release without the fftw3
>  > dependency. Is there a way to turn off linking with fftw3 during the
>  > scipy build process, even if fftw3 is present on the system? I can
>  > disable fftw3 via MacPorts, build, then re-enable, but I'd prefer to
>  > keep the build process a little more contained. Forgive me if rkern's
>  > already told us all how to do this years ago...
>  >
>  You can do something like
>
>  FFTW3=None python setup.py build
>
>  This works for any library, actually (you can do ATLAS=None, etc...).
>
>  cheers,
>
>  David
>  _______________________________________________
>  SciPy-user mailing list
>  SciPy-user at scipy.org
>  http://projects.scipy.org/mailman/listinfo/scipy-user
>