Thanks for the pointers, Thiago and Rainer! I'm sure these will get me moving
forward again.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Am 04.12.2013 07:25, schrieb Thiago Macieira:
On quarta-feira, 4 de dezembro de 2013 06:20:45, Rainer Wiesenfarth wrote:
What we did in addition for our software is to add these options to the
Qt configure:
-buildkey namexyz -no-rpath -R $ORIGIN
This was used to prevent 'our' QtCore4.so (?
On quarta-feira, 4 de dezembro de 2013 06:20:45, Rainer Wiesenfarth wrote:
> What we did in addition for our software is to add these options to the
> Qt configure:
>
>-buildkey namexyz -no-rpath -R $ORIGIN
>
> This was used to prevent 'our' QtCore4.so (?) from loading
> system-installed plug
Am 04.12.2013 05:58, schrieb Thiago Macieira:
On terça-feira, 3 de dezembro de 2013 19:51:44, Bob Hood wrote:
[...]
However, the plug-in shared libraries don't seem to be adhering to this
redirection mechanism. If I deploy to a "clean" installation of my Linux
distribution, the shared libraries
On terça-feira, 3 de dezembro de 2013 19:51:44, Bob Hood wrote:
> There's probably an obvious solution to this, so forgive me if so.
>
> I'm building an Qt-based application that uses shared libraries as plug-ins.
> Both the application and the plug-ins link to the Qt libraries in my
> installatio
