On Tuesday 10 September 2013 11:13:59 Pali Rohár wrote: > On Tuesday 10 September 2013 11:03:56 Jan Kundrát wrote: > > On Sunday, 8 September 2013 14:19:02 CEST, Pali Rohár wrote: > > > Maybe another (funny) solution for loading plugins from > > > build directory (without installing). Support for loading > > > shared libraries from build directory is already done by > > > cmake via adding build directory to rpath to all ELF > > > binaries. When binaries are installing, cmake removing > > > rpaths. So what about loading plugins from rpaths? It is > > > even possible to read rpath in application? > > > > Well, the impression I get from this is that rpath is > > actually *exactly* what we are looking for. Cmake handles > > it for us by default and it is *the* tool for specifying > > custom library search path on Unix. It's a pity that > > QPluginLoader probably does not respect that settings. > > > > I'll think about this a bit more. > > > > Cheers, > > Jan > > QPluginLoader does not do anything with any directory. You > need to tell full path (or relative) to library which you > want to use.
Or another option is maybe to use qLoadPlugin() and class QFactoryLoader. It doing what we want (specify plugin string ID and it will magically find it and load) - but this library is Qt private :-( -- Pali Rohár pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
