Just my two cents here : 1. As far as I know, msvcr71.dll is installed to system32 if you choose to install python "for all users". On the other hand, installing for the current user only copies msvcr71.dll to the python directories, which makes sense as you might not have write access to C:\Windows\System32. 2. the pygoject and pygtk installers rely on msvcr71.dll because distutils uses wininst-7.1.exe (in Python25/Lib/distutils/command) by default to build these installers. I could try to repackage pygobject and pygtk with wininst-6.exe though. 3. python requires msvcr71.dll while GTK+ is built on win32 against good old msvcrt.dll. As mixing runtime environments is supposed to be a bad idea, I decided to use the default distutils linking options (msvcr71.dll). Feel free to report any problems related to runtime mixing though.
Cédric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Ehresman Sent: Thursday, August 23, 2007 5:10 PM To: John Pye Cc: pygtk Subject: Re: [pygtk] problem installing PyGTK on a clean WinXP system John Pye wrote: > That was a good thought; I missed that. The installer executable itself > is broken. Which confirms that this is an issue with distutils. Yes, it does look like the pyobject installer .exe is relying on msvcr71.dll being available -- which is a bad assumption because it is not an operating system provided .dll. I suggest that the next step is to report or fix the bug in that installer (or not use it and just install the files directly). Cheers, John _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
