RE: glibc warnings

>Ideally my application would link dynamically to Qt, and then the
>autopackage would determine if Qt 4.2+ is already present.  
>If it isn't, then there'd be some internal qt.package file that 
>gets installed.  However, I haven't figured out how to do that 
>yet so I thought the easiest approach would be to do a static build.

You can use RPATH on you binaries.

Set rpath to "/opt/some/private/location/qt4.2" and have your qt.package
install libraries in this location in case they are needed. (You can
also set rpath relative to executable).

Don't forget to set rpath on Qt libs themselves, so QtGui finds your
copy of QtCore before system's one (in case both are present).

Your binaries will always use private Qt if it is installed and fallback
to system Qt if it is not. Then you can implement appropriate logic in
autopackage install script.

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