On Monday 12 August 2013 18:25:40 Jan Kundrát wrote: > On Sunday, 11 August 2013 12:45:23 CEST, Pali Rohár wrote: > > So do you think that this is real problem? > > Maybe not really, after all. However, what about adding a code > which checks whether the qApp->applicationDir() matches the > cmake's binary output path and if that is the case, it > disabled the plugin lookup in appdir? The same change should > be made for the l10n lookups, IMHO. > > In case you like this, are going to patch it, or shall I do it > for l10n? > > Cheers, > Jan
I do not like idea to include compile output path into binaries. This sounds like that something is bad if some random path (=compile path) must be present in application executable. Also there can be lot of other problems with this. If user move trojita source/build tree to another location it will break loading plugins of already compiled trojita binary. And if somebody want to use trojita without install it into system (portable version), then it will not work too, if he move trojita binary to other directory/disk/mount point. -- Pali Rohár pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
