On Fri, 30 Mar 2001, Skip Montanaro wrote:
>
> James> I just put up a new snapshot of devel pygtk at:
> James> http://www.gnome.org/~james/pygtk2-SNAP-20010330.tar.gz
>
> James> It requires python >= 2.0 and recent CVS checkouts of glib, pango
> James> and gtk+ to compile. It is not fully up to date with all the API
> James> additions/changes, but it compiles and runs.
>
> *sigh*...
>
> I realize the gnome folks are trying to do me a favor by making it harder
> for me to build glib, pango and gtk+ so that it is correspondingly harder to
> shoot myself in the foot, but I'd like to experiment with James's new
> release and find it frustrating that I should need to know the ins and outs
> of autoconf and/or automake. Would someone please tell me how to create
> ./configure? I tried "autoconf" in the glib dir and got a configure script,
> but also this error (and a bunch of warnings about AC_TRY_RUN):
I have never tried building gtk on win32, so probably won't be able to
help that much. From posts to gtk-devel-list, it sounds like you need CVS
libtool in order to compile it on win32. I don't know about the other
details.
It probably has build problems on x11 too, because the gtk-2.0.m4 autoconf
macro I was using is broken (it uses gtk-config-2.0 macro, which doesn't
exist anymore -- there is a bug in bugzilla about this).
As far as pygtk goes, you probably want to use the snapshot tarball,
rather than CVS, as the tarball is built with the CVS version of automake
(needed for python support).
James.
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
