Aha, On Sun, Apr 27, 2014 at 3:19 PM, Matthew Brett <matthew.br...@gmail.com> wrote: > Hi, > > On Sun, Apr 27, 2014 at 3:06 PM, Carl Kleffner <cmkleff...@gmail.com> wrote: >> A possible option is to install the toolchain inside site-packages and to >> deploy it as PYPI wheel or wininst packages. The PATH to the toolchain could >> be extended during import of the package. But I have no idea, whats the best >> strategy to additionaly install ATLAS or other third party libraries. > > Maybe we could provide ATLAS binaries for 32 / 64 bit as part of the > devkit package. It sounds like OpenBLAS will be much easier to build, > so we could start with ATLAS binaries as a default, expecting OpenBLAS > to be built more often with the toolchain. I think that's how numpy > binary installers are built at the moment - using old binary builds of > ATLAS. > > I'm happy to provide the builds of ATLAS - e.g. here: > > https://nipy.bic.berkeley.edu/scipy_installers/atlas_builds
I just found the official numpy binary builds of ATLAS: https://github.com/numpy/vendor/tree/master/binaries But - they are from an old version of ATLAS / Lapack, and only for 32-bit. David - what say we update these to latest ATLAS stable? Cheers, Matthew _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
