On Thu, May 31, 2012 at 1:55 PM, Joao S. O. Bueno <gwidion@xxxxxxxxxx> wrote: > On 31 May 2012 12:53, Kevin Cozens <kevin@xxxxxxxxx> wrote: >> On 12-05-29 11:55 AM, Jernej Simončič wrote: >>> >>> Neither - PyGimp on Windows is always 32-bit, so I suspect it's >>> looking for translations relatively to the 32-bit DLL directory. >> >> >> If a person wants to compile GIMP for 64-bit why is pygimp still only >> 32-bit? Known compatability issues? No one has gotten around to testing >> 64-bit? Or could it be as simple as no one has bothered to update the build >> method for pygimp? >> >> It seems odd to me to mix 32-bit and 64-bit in parts of a program that all >> come out of the same source tree. > > > Last I checked, there is no native PyGTK+ for Windows 64bit, due to > the fact the binary signatures used by GCC in win 64 (used in gobject, > gtk+) and visualstudio (used for Python) are different. > > I do not use Windows, and have no idea if this has changed. Since > pyGIMP works as an off-process plug-in, if it works, it is the way to > go, because there would not be a feasible work-around. > > I intend to research and update pygimp to use gobject introspection > during gimp 2.9 - maybe that can allow for a 64bit version of it on > Windows. > > (It is important to note that such problems do not happen under Linux > - and that there are other problems due to not using gobject > introspection under mac os x) > > js > -><- >> >> >> -- >> Cheers! >> >> Kevin. >> > _______________________________________________ > gimp-developer-list mailing list > gimp-developer-list@xxxxxxxxx > https://mail.gnome.org/mailman/listinfo/gimp-developer-list Not true. This was one of the reasons that I started my own builds. In my build, Python is 64-bit. Partha _______________________________________________ gimp-developer-list mailing list gimp-developer-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gimp-developer-list
