[pygtk] Call For Testing: Updated PyGObject, Pycairo and PyGTK for Windows

Dieter Verfaillie dieterv at optionexplicit.be
Thu Oct 28 17:12:00 WST 2010


Hi,

Quoting "John Stowers" <john.stowers.lists at gmail.com>:
> Yeah, styles is something different. Can you please run the installer
> from the console and see if it prints anything else of interest please?
>
> What is your target system, etc?
>
> Does anyone else have any ideas on this?

This might be caused by leftover files from a previous installation.
At least, the error stopped for me once I manually cleaned my pyg*
environment last year.

Uninstall pygtk, pygobject, pycairo (and other pyg* bindings if you
have them) and manually delete the following (if those files/dirs
are still there...):
<pythonroot>\include\pycairo
<pythonroot>\include\pygtk-2.0
<pythonroot>\Lib\pkgconfig
<pythonroot>\Lib\site-packages\cairo
<pythonroot>\Lib\site-packages\gtk-2.0
<pythonroot>\Lib\site-packages\pygtk*
<pythonroot>\share\gtk-doc
<pythonroot>\share\pygobject
<pythonroot>\share\pygtk

Then reinstall pycairo, pygobject and pygtk. If you still get the error
after that, I'd like to know about it. That would mean something goes
wrong when the pkgconfig file gets fixed during the installation
process (in postinstall).

John: I'll investigate if it's possible to fix the pkgconfig
file at build time instead of the current postinstall procedure.
That way we can drop postinstall altogether and .msi
installers can have a working environment too (as those don't
support postinstall)...

hth,
Dieter

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


More information about the pygtk mailing list