I think this is doable; thankfully the Intel compilers on Windows and Linux are very similar in behavior. The exact same build scripts should work fine provided the file extensions (.o --> .obj) and flags (-L, etc.) are modified. In terms of syntax this should be an easy thing to do (it was with the free-standing F2PY) , but I will need some help navigating through the magic you refer to. I will put some effort into this and write back if I hit a roadblock. As an aside: how were the Windows 32-bit installers created? Is it possible to recreate this process changing the target arch --> x64?

   Thanks again,
   ~Mike C.

On Wed, Jan 28, 2009 at 1:06 AM, David Cournapeau <david@ar.media.kyoto-u.ac.jp> wrote:
Michael Colonno wrote:
>    Thanks for your response. I manually edited one of the python files
> (ccompiler.py I think) to change icc.exe to icl.exe. (This is a trick
> I used to use to get F2PY to compile on Windows platforms.) Since icl
> is a drop-in replacement for the visual studio compiler / linker, I'd
> like to edit the python files configuring this (msvc) but I could not
> find anything(?) If you could point me towards the config files(s) for
> the visual studio compiler (I'm assuming are configured for the
> Windows file extensions already) I could likely make some headway.`

Unfortunately, the code for our building process is difficult to grasp -
there is a lof of magic. Everything is in numpy/distutils. Basically,
you need to create a new compiler, a bit like intelccompiler.py, but for
Windows. I unfortunately can't help you more ATM, since I don't know the
intel compiler on Windows.


Numpy-discussion mailing list