JW enlightened us with:
> Thanks to Michael and Nick, I can now cross-compile my Pyrex
> extensions for bog-standard Python 2.5 [...] I can now use Linux to
> cross-build my extension for Windows, and my preliminary testing
> (under WINE -- See the original post. I must adhere to my
> employment c
Thanks to Michael and Nick, I can now cross-compile my Pyrex extensions
for bog-standard Python 2.5. As I stumbled around in the dark trying to
bump into a solution, I was bolstered by the belief that at least two
other people had found the light at the end of the tunnel.
I had been using a cruft
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> To build an extension that runs on a generic python 2.5 you need a
> Windows OS (suprise!) and VS.NET 2003. Some people may have had some
> success with MinGW32 (on windows) but it's not going to work
> 'out-of-the-box'.
Neither of those statemen
JW <[EMAIL PROTECTED]> wrote:
> I have a lousy little Python extension, generated with the generous help
> of Pyrex. In Linux, things are simple. I compile the extension, link it
> against some C stuff, and *poof*! everything works.
;-)
> My employer wants me to create a Windows version of
On Fri, 2006-10-13 at 11:39 -0400, JW wrote:
> I have a lousy little Python extension, generated with the generous help
> of Pyrex. In Linux, things are simple. I compile the extension, link it
> against some C stuff, and *poof*! everything works.
>
> My employer wants me to create a Windows ver
JW wrote:
>
> My main problem is that I don't really grasp the big picture. Can someone
> give me an overview of the requirements to build extensions for Windows
> Python, circa 2.5? Or, can I tell my employer she'll just have to
> hire/contract a Windows expert to do the mud wrestling?
>
> Jim
