(snip) > Well, Visual Studio is preferred by the Python core devs. MinGW works > too, with some gotchas here and there due to mixing different > c libraries at runtime. For example: > - msvcrt used by the GTK+ runtime and PyGTK when built with MinGW > - msvcr90 used by Python 2.6 and newer > In this case a function (from GIO for example) that returns a file > descriptor is useless from Python code and vice versa. I guess you are using MinGW for the 32-bit aio then. It makes sense to do the same thing for 64-bit.
> Other than that, building Python extensions with MinGW works fine. OK. (snip) >> Can you just confirm whether I should be using >> MinGW or VC2008? > > MinGW might be the path of least resistance, don't think anyone has > given PyGObject's dsextras.py and PyGObject's+PyGTK's setup.py msvc > support code any attention for a couple of years. I'm pretty sure > PyGTK-2.12 was the last release actually built with msvc... OK, I am a bit short on time (as always), but I'll try to setup a 64-bit XP virtual machine we can all access (and trash if needed). Cheers Antoine _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
