Cedric, I recently have many emails that report similar problems. I think I cannot write an explanation as good as yours due to my bad english. Would you mind that I include this post in my upcoming FAQ?
Cheers, Ivan. >vector wrote: >> yeah well been there tried that and gave up.Please let me know if you >> get it to work or you can update my twiki site >> http://mec-symonds.eng.monash.edu.au/cgi-bin/twiki/view/Saqqara/Gtk4Win32 >> where i have documented my failures. the problem seems to be that the >> developers of glade,gtk and pygtk are all working at different version >> levels and putting things in different folders where others cant find >> the path. Most support here is for the linux brand. I think the only >> real way to solve this it to actually build or make the files on your >> win box but that is also a mountain of pain that I havent attempted to >> climb. I currently cant use glade but did get pygtk, gtk and python >> working fine. >> BTW on linux it," just works"! > >It looks to me from your wiki that you might have multiple, incompatible >versions of the GTK+ runtime currently installed on your computer. >Welcome to DLL hell ! > >Just for the sake of it, I have just installed GTK+ + pygtk on a win2k >box and ran the pygtk-demo in less than 2 minutes. > >By the way, I have updated my pygtk page to recommend the gladewin32 >installer, even with pygtk-2.2. The gladewin32 installer seems to be the >de-facto standard this days. It is actively and very well maintained. > >So, here we go again > >1. Remove all previous installations of GTK+ and pygtk. That means GTK+ >from gladewin32, dropline, Dev-Cpp, gimp, gaim, you name it... Then >carefully look in Windows\system32 for any GTK+-related leftover DLLs, >in particular iconv.dll, libintl.dll, libxml2.dll, intl-1.dll and all >the libg*.dll and g*.dll with a GTK+ name (gobject, gthread, atk, pango,...) > >2. Install the GTK+ runtime from gladewin32 > >http://prdownloads.sourceforge.net/gladewin32/gtk-win32-2.4.9-rc1.exe?downl oad > >Make sure that the "Register environment variable" is selected (this >should be the default) > >3. Run the Gtk-demo (Start menu/Gtk/Gtk-demo). Does it work ? If no, >please post the error message in this thread. > >4. Try to run a simple helloworld example >http://www.pcpm.ucl.ac.be/~gustin/win32_ports/binaries/helloworld.zip >Unzip helloworld.exe and double-click on it (no need to open a console). >Does it work ? If no, please post the error message in this thread. > >5. Install pygtk-2.2 or pygtk-2.3.x (your choice) > >http://www.pcpm.ucl.ac.be/~gustin/win32_ports/binaries/pygtk-2.2.0-1.win32- py2.3.exe > >http://www.pcpm.ucl.ac.be/~gustin/win32_ports/binaries/pygtk-2.3.96.win32-p y2.3.exe > >6. From python (command line, python ide, pythonwin), try "import pygtk" >and "import gtk" > >7. download the pygtk tarball >http://ftp.gnome.org/pub/GNOME/sources/pygtk/2.2/pygtk-2.2.0.tar.gz >Untar it and try to run examples/pygtk-demo/pygtk-demo.py. It should >work out of the box. Report any problem. > >In a regular installation, only steps 2 and 5 should be required. i have >tested that config on 20+ machines without any problem. > >Hope it helps > >Cedric > _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
