Re: QT install and search paths

[Hartmut Goebel]

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          | address@hidden               |
| www.crazy-compilers.com | compilers which you thought are impossible |