all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org, iyzsong@gmail.com
Subject: Re: QT install and search paths
Date: Fri, 25 Aug 2017 09:32:32 +0200	[thread overview]
Message-ID: <5af4a60b-b096-84cb-c72f-256051c2e6fe@crazy-compilers.com> (raw)
In-Reply-To: <20170824.133749.1478354122253631402.post@thomasdanckaert.be>

Am 24.08.2017 um 13:37 schrieb Thomas Danckaert:
> Either way, I think qtbase's QT_PLUGIN_PATH setting only has an effect
> if a user installs qtbase directly in their profile […] so
> applications using these plugins will still need to set the correct
> environment variable themselves somehow?

Do my understanding, "search-paths" will make the the listed paths of
all installed packages to be added to the named variable. Thus in this
case the package would "just" need to ensure all it's dependencies are
installed. The rest is done automatically.

Which leads to another, different problem: For this to work AFAIU the
package needs to propagate all the plugins, etc. it is using. Which is
not nice, and which I assume is the resume from

> https://lists.gnu.org/archive/html/guix-devel/2016-12/msg00776.html
>
> For the kdevelop package, I wrapped the executable, setting a bunch of
> Qt-related environment variables.  This works as a stop-gap, but it
> will break down when a user uses multiple Qt/KDE applications with
> different plugin requirements (some KDE daemons, such as kdeinit, need
> to find all their plugins at the moment they are started).

Nice idea! But unfortunately this is not a solution in the long term –
since it would require this to be done for each and every KDE and even
QT application.

> Ludo suggested using a profile hook to set the required environment
> variables depending on the installed applications, but I never looked
> into it further because wrapping the executable was “good enough”
> for.  For a KDE desktop, I think you'll need a better solution. 

I'd appreciate if you could have a look at this. I have some other todos
on my lit with higher priority, but this problems are a show-stopper for
my efforts on the plasma-desktop (which are much more time-consuming
than I thought).

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  reply	other threads:[~2017-08-25  7:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 18:25 QT install and search paths Hartmut Goebel
2017-08-24 11:37 ` Thomas Danckaert
2017-08-25  7:32   ` Hartmut Goebel [this message]
2017-08-24 11:59 ` 宋文武
2017-08-25  7:06   ` Hartmut Goebel
2017-08-25 12:40     ` 宋文武
2017-08-25 16:04       ` 宋文武
2017-08-26  8:31         ` Hartmut Goebel
2017-08-27 16:49         ` Hartmut Goebel
2017-09-02 16:40           ` Hartmut Goebel
2017-09-03  4:58             ` 宋文武
2017-09-03 11:46               ` 宋文武
2017-09-03 12:39                 ` Hartmut Goebel
2017-09-03 14:04                 ` Hartmut Goebel
2017-09-03 14:46                   ` 宋文武
2017-09-04  7:44             ` Thomas Danckaert
2017-09-04  9:16               ` Hartmut Goebel
2017-09-07 13:38                 ` 宋文武
2017-09-19 16:30                   ` Hartmut Goebel
2017-09-22 12:59                     ` Hartmut Goebel
2017-10-06 12:22                   ` Hartmut Goebel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5af4a60b-b096-84cb-c72f-256051c2e6fe@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@gmail.com \
    --cc=post@thomasdanckaert.be \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.