From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: IBus and different GTK versions
Date: Mon, 14 Sep 2015 10:06:16 +0200 [thread overview]
Message-ID: <87zj0pv30n.fsf@gnu.org> (raw)
In-Reply-To: <87mvwq35c4.fsf@gmail.com> ("宋文武"'s message of "Sun, 13 Sep 2015 19:51:23 +0800")
宋文武 <iyzsong@gmail.com> skribis:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> [...]
>>
>> It seems that GTK3 only looks for
>> ‘$libdir/gtk-3.0/3.0.0/immodules.cache’ and GTK2 only looks for
>> ‘$libdir/gtk-2.0/2.10.0/immodules.cache’ by default, where ‘$libdir’ is
>> ‘$out/lib’ of the GTK package. (According to
>> https://developer.gnome.org/gtk3/stable/gtk-running.html)
>>
>> To make IBus work we need to find a way to make the different major
>> versions of GTK respect different ‘immodules.cache’ files that are *not*
>> located in their ‘$libdir’. In that case we could generate a fresh
>> ‘immodules.cache’ file for each major GTK version when building a
>> profile. Unfortunately, I haven’t been able to find any documented
>> means to achieve this. It might require patching the GTKs to check an
>> additional path or environment variable.
>>
> We can set 'GTK_EXE_PREFIX' to the '~/.guix-profile', and generate the
> 'immodules.cache' files in a profile hook. It will work for both gtk2
> and gtk3 applications.
What other things does ‘GTK_EXE_PREFIX’ affect?
The plan you suggest sounds good to me, my only concern is whether
‘GTK_EXE_PREFIX’ is too broad for our purposes.
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-09-14 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 11:27 IBus and different GTK versions Ricardo Wurmus
2015-09-13 11:51 ` 宋文武
2015-09-14 8:06 ` Ludovic Courtès [this message]
2015-09-14 8:28 ` Ricardo Wurmus
2015-09-14 9:18 ` 宋文武
2015-09-15 19:16 ` Ricardo Wurmus
2015-09-20 17:12 ` Ricardo Wurmus
2015-09-20 18:25 ` Ricardo Wurmus
2015-09-21 16:06 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj0pv30n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).