On Mar 2, 3:08 pm, "Alex Nolley" <[email protected]> wrote:
> Istvan, what would be the point of me working in VS2003 if people with later > versions won't be able to compile my module? MinGW seems to work fine for > compiling my code on Windows. The only advantage I see with coding in VS2003 The sole reason for using VS2003 is to compile extensions with the same compiler that was used to create the main python distribution. That way whatever you compile is guaranteed to work with Python. But if you have everything working with Mingw then that's great nothing more needs to be done. Just make sure that it actually works on someone else's computer too, sometimes you can end up linking to some DLLs that only you have so it only works if the other party also installs Mingw (or cygwin). Since I have Visual Studio I've never needed to investigate how well MingW works, in fact I am curious to see whether the MingW alternative works out well or not. You should put onto the wiki what you have done to compile it with Mingw (or update the existing page if there's one). > Alex, Istvan -- another question is, what would be the right compiler to > use for distributing binary releases to people? For me this usually means compiling the extensions with the compiler that was used to create python. I believe for python 2.6 they switched to Visual Studio 2007 while both 2.4 and 2.5 were done with VS 2003 Istvan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
