[Numpy-discussion] Building Windows binaries on OS X
Tue Feb 9 05:05:25 CST 2010
On Tue, Feb 9, 2010 at 9:54 AM, David Cournapeau <firstname.lastname@example.org> wrote:
> On Mon, Feb 8, 2010 at 9:14 PM, Ralf Gommers
> <email@example.com> wrote:
> > Hi David and all,
> > I have a few questions on setting up the build environment on OS X for
> > Windows binaries. I have Wine installed with Python 2.5 and 2.6, MakeNsis
> > and MinGW. The first question is what is meant in the Paver script by
> > plugin". Wine seems to know what to do with a cpuid instruction, but I
> > not find a plugin. Searching for "cpuid plugin" turns up nothing except
> > NumPy pavement.py file. What is this?
> That's a small NSIS plugin to detect at install time the exact
> capabilities of the CPU (SSE2, SSE3, etc...). The sources are found in
> tools/win32build/cpucaps, and should be built with mingw (Visual
> Studio is not supported, it uses gcc-specific inline assembly). You
> then copy the dll into the plugin directory of nsis.
Yep got it. There's quite some stuff hidden in tools/ and vendor/ that I
never noticed before.
> > Final question is about Atlas and friends. Is 3.8.3 the best version to
> > install? Does it compile out of the box under Wine? Is this page
> > http://www.scipy.org/Installing_SciPy/Windows still up-to-date with
> > to the Lapack/Atlas info and does it apply for Wine?
> Atlas 3.9.x should not be used, it is too unstable IMO (it is a dev
> version after all, and windows receives little testing compared to
> unix). I will put the Atlas binaries I am using somewhere
That would be *great*.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion