It should install into pygtk/2.0; that is normal. The 2.0 indicates that it is API/ABI compatible with pygtk 2.0. As long as there are no backwards-incompatible changes, the directory remains 2.0, even for version 2.4. Are you on linux? If you are, then the only things you should really need to build yourself are babl, gegl, and gimp. Install your distro's packages for everything else, and you should be good to go. If you have issues with python, then you may need to do this before running gimp's autogen.sh: export PYTHON="/usr/bin/python2" Good luck. On Sun, Aug 4, 2013 at 3:26 PM, Burnie West <west@xxxxxxxx> wrote: > On 08/04/2013 10:41 AM, Burnie West wrote: >> >> And I already had pygtk/2.0 installed natively. >> > But for some reason, even though the installation is in fact pygtk2-2.24.0, > it installs in the directory pygtk/2.0 (Fedora 18), as I had noted earlier. > I've very little experience with the configure script; indeed, little > expreience with console scripting. But it appears the configure script > cannot cope with this formulation, and I'm currently attempting to find out > why. > > As my current intent is to work on python plugins (a particular one in > fact), building My-gimp without python support is a non-starter. I'd already > successfully built babl, gegl, and gimp-2.9.0 about a year ago, but had > disabled the python section (as lightningismyname had suggested) and dropped > that path. > > _______________________________________________ > gimp-developer-list mailing list > List address: gimp-developer-list@xxxxxxxxx > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
