After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 304806 - Incorrect paths in gtk.immodules file prevent loading
Incorrect paths in gtk.immodules file prevent loading
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.6.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
: 305837 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-05-19 21:13 UTC by Daniel Atallah
Modified: 2005-06-01 21:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Atallah 2005-05-19 21:13:55 UTC 
In the win32 GTK 2.6.7 binaries, the paths seem to be incorrect in the
gtk.immodules file so that the installation directory conversion doesn't work.

The paths are different than those in gdk-pixbuf.loaders
gtk.immodules     ="c:/devel/target/2.6/lib/gtk-2.0/2.4.0/..."
gdk-pixbuf.loaders="c:/devel/target/gtk+-2.6.7/lib/gtk-2.0/2.4.0/..."

As I'm looking into this, i'm noticing that the code that does the runtime path
conversion is different for the pixbuf loader paths than it is for the
gtk.immodules.  The pixbuf loader conversion uses GTK_PREFIX and the immodules
uses GTK_LIBDIR (yes, I noticed that gtkprivate.h isn't included to give it the
dynamic definition, but is it still right?).

I'm not sure if this is an error in the build or an error in the code (or both).
Comment 1 Tor Lillqvist 2005-05-19 21:48:58 UTC 
Oops. Error in packaging/building. The code should be OK. The gtk.immodules is
the one that's broken, it should have paths starting with
c:/devel/target/gtk+-2.6.7/, too. I have updated the zipfile on ftp.gtk.org.
Comment 2 Tor Lillqvist 2005-06-01 21:43:52 UTC 
*** Bug 305837 has been marked as a duplicate of this bug. ***