Brian E Gallew wrote: >Then <[EMAIL PROTECTED]> spoke up and said: > >>First of all, are you talking about porting pygtk on cygwin using XFree >>(http://cygwin.com/xfree/) or the win32 port of gtk+ (as available from >>http://www.gimp.org/win32/) ? If you plan to use XFree, things should be >> > >xfree. I'm a unix sysadmin and would normally run linux or freebsd on >my laptop, but it turns out I also need access to Windows software. >My solution is to use the cygwin package with the cygwin port of >xfree. It works extremely well, and building packages mostly just works. > >>P.S. : what do you mean by "the binary package is not cygwin friendly". You >>use python as provided by the cygwin distribution ? If it's the case, you >>must use XFree and port gtk+ and pygtk accordingly. >> > >Exactly. Sorry, I should have specifically mentioned xfree. In any >event, it configures/builds just fine, except that when I try to use >it, I discover that none of the widgets exist. > >>pretty straightforward using the configure script. You might have to fight >>with dlltool/dllwrap to generate the _gtk.pyd though. If you want to use >> > >What's a .pyd? Also, there doesn't seem to be a Makefile rule for the >creation of _gtk.py*. Perhaps this is my problem? > For some reason, with the windows version of python, they sometimes rename the dll extension modules to the extension .pyd (they are still dlls).
The pygtk build should build and install a shared library called _gtkmodule.dll. Does htis build okay on cygwin? It is possible that the problem you are seeing is that the GTK.py file overwrote the gtk.py file when unpacking the tarball. This problem has been fixed on the development branch, but remains broken on the stable branch (renaming the module would break compatibility). James. -- Email: [EMAIL PROTECTED] WWW: http://www.daa.com.au/~james/ _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
