[Interest] Qt 5.x and Plugin-Build-Key

[Christoph Cullmann]

Hi,

for our commercial application, we ship the Qt dynamic libraries in our package,
as we can't rely on the system libs to be up-to-date enough.

In Qt 4.x, we used the build-key of the plugins to disallow qt plugins of the system
to be loaded, should there be some Qt 4.x stuff installed.

(http://qt-project.org/doc/qt-4.8/deployment-plugins.html#the-build-key)

For Qt 5.x, that "feature" seems to have gone.

If I now install our application on some system having e.g. KF5 installed,
it will instantly segfault on launch as it will find the platform integration
plugin of KF5 (that is linked against system Qt5 that is not compatible to our build,
because of different g++ and Co.)

Is there a way to block any loading of plugins not bundled like in Qt 4.x with the build-key?
(Without relying on some shell script purging QT_PLUGIN_... env vars?)

Greetings
Christoph

-- 
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH      Email: cullmann at AbsInt.com
Science Park 1                         Tel:   +49-681-38360-22
66123 Saarbrücken                      Fax:   +49-681-38360-20
GERMANY                                WWW:   http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234