|
From: | Jonathan Kinsey |
Subject: | RE: [Bug-gnubg] Win gcc3 / gcc43 / gcc44 |
Date: | Thu, 25 Jun 2009 11:39:21 +0000 |
I doubt it's worth moving up to 2.6.1, better to move to version 3. It will take a few changes though. I just built Python 3 with dev studio and made some changes to get gnubg to build, namely: PyInt -> PyLong PyString -> PyUnicode (needs more work) Py_InitModule -> PyModule_Create It didn't quite work (importing gnubg module fails), but I guess it's not to far away. It can't be too hard to build (or get) a mingw python3 lib/dll. I don't really use Python so it's low priority for me. Jon To: address@hidden CC: address@hidden Subject: Re: [Bug-gnubg] Win gcc3 / gcc43 / gcc44 From: address@hidden Date: Thu, 25 Jun 2009 12:54:49 +0200 Jonathan Kinsey <address@hidden> wrote on 25/06/2009 11:07:26: > I'm not sure if I was compiling this code, I'll double check. The > 'z' should be valid, but I doubt it's important OK. > and you can probably comment out the #define > in pyconfig.h. > > Or you could temporarily build without python to see if 4.4 works for you in > general. > > BTW I'm using Python 2.6.1 here. I'll try to move to python 2.6. One question: for 2,5 we needed pymingw extension to make python work with mingw: is it still needed for 2.6 ? Hope it's not, since there's no pymingw for 2.6 ... MaX. View your Twitter and Flickr updates from one place – Learn more! |
[Prev in Thread] | Current Thread | [Next in Thread] |