RE: autopackage of qt

> Do I also need to set the rpath of the Qt libraries themselves?=20
> What about on plugins that I may load? =20
> Or will all of them use the app's rpath?

Yes, both on libraries and on plugins. If you use ORIGIN rpath (and you sho=
uld), all rpaths start from the location of whatever binary it is set on.

So if you have layout like this:

/opt/private/bin/theapp
/opt/private/lib/libQtCore.so.4
/opt/private/plugins/imageformats/libqjpeg.so=20

theapp should have rpath at least "$ORIGIN/../lib"
libQtCore.so.4 should have "$ORIGIN"
and plugin should have "$ORIGIN/../../lib"

It is a bit of pain to set up in build projects themselves, so I just make =
sure any rpath is set at all, and then change it with chrpath to proper loc=
ation during installation build.

Also, since you are building Qt yourself, make sure to set same buildkey fo=
r Qt, its plugins and your app. (otherwise plugins will not load). If you b=
uild everything with same compiler it should be same though.

Also :). Don't forget to write out qt.conf (goes into /opt/private/bin/ in =
example) with location of plugin paths and settings and whatnot. Otherwise =
Qt might look in random places and you don't want that.



---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]