Plugins path in master branch

[Jack]

I think this is related to an issue I ran into trying to have more than  
one version of KMM installed on my system at the same time (in my case,  
both production and development version of 4.x).  It is easy enough to  
actually install them to different places, but much of where KDE looks  
for things at runtime (icons, themes, plugins, ....) is controlled by  
environment variables, so you have to be careful that you don't run one  
executable which then finds the plugins compiled for the other  
version.  (In addition, KDE caches much of this stuff, which is reset  
by kbuildsycoca4 or 5 (build system configuration cache)).

Basically, this means there needs to be some coordination in settings  
between compile time and runtime.

I suspect it's even more an issue when mixing KDE4 and Frameworks, such  
as compiling for one under the other.


Jack

On 2016.06.20 08:25, Cristian Oneț wrote:
> No, that will be handled by distros. If you now need to set
> QT_PLUGIN_PATH that means you are not building kmymoeny according to
> the way your distro does. Simply installing kmymoney in the system
> folders (by running sudo make install) is not enough if you the
> destination is not properly setup during configure. Someone please
> step in and explain this better.
> 
> Regards,
> Cristian
> 
> 2016-06-19 21:28 GMT+03:00 Łukasz Wojniłowicz  
> <lukasz.wojnilowicz at gmail.com>:
> > What about final 5.0 version? Will the user be required to set  
> QT_PLUGIN_PATH?
> > I didn't have to set any variable in previous master branch.
> >
> > Dnia niedziela, 19 czerwca 2016 10:19:06  
> kmymoney-devel-request at kde.org pisze:
> >> Message: 4
> >> Date: Sun, 19 Jun 2016 11:43:25 +0200
> >> From: onet.cristian at gmail.com
> >> To: For KMyMoney development <kmymoney-devel at kde.org>
> >> Subject: Re: Plugins path in master branch
> >> Message-ID: <7AF8A229-2701-4058-8EA1-D802CD6B7DC4 at gmail.com>
> >> Content-Type: text/plain;       charset=utf-8
> >>
> >> The same applies, just set the prefix to the proper value and it  
> will work.
> >
>