Base Directory Specification and plugins

[Yury G. Kudryashov]

David Faure wrote:

> On Sunday 11 December 2011 15:16:32 Yury G.  Kudryashov wrote:
>> Plugins should be installed to
>> ${INSTALL_PREFIX}/lib${LIB_SUFFIX}${LIBRARY_SPECIFIC_SUFFIX}.
>> ${LIB_SUFFIX} should be chosen in the same way that is used for shared
>> libraries.
>> 
>> Buildsystem of a plugin-enabled library/application should (must?) allow
>> distributions to override LIB_SUFFIX and may allow override of
>> LIBRARY_SPECEFIC_SUFIX.
> 
> Overriding the library suffix? If you install a plugin for qt, it has to
> go into /usr/lib/plugins/qt, if that's where all your qt plugins go. If a
> single plugin is compiled with an overriden library suffix of "foobar",
> then your plugin /usr/lib/plugins/foobar will feel quite alone and ignored
> :)
Overriding the LIBRARY_SPECIFIC_SIFFIX while compiling the library, not a 
plugin. E.g., `./configure --plugin-suffix=qt` for plugins in 
$prefix/lib/plugins/qt or `./configure --plugin-suffix=qt4` for plugins in 
$prefix/lib/plugins/qt4.

Later every package that wants to install a plugin will read this setting 
from QtCore.pc or QtConfig.cmake.
>> Both LIB_SUFFIX ad LIBRARY_SPECIFIC_SUFFIX must be advertised through
>> installed development files (e.g., mylib.pc or MyLibConfig.cmake).
> 
> Yes (well, or just the full path where to install plugins?)
Either both parts or the full path _relative_ to the installation prefix. 
The absolute path makes no sense if I'm installing a plugin to my home 
directory.
-- 
Yury G. Kudryashov,
mailto: urkud at mccme.ru