Re: glibc warnings

2007/11/28, Eugene Zolenko <EugeneZolenko-XYgkjQFSZqy1Z/[email protected]>:
> >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.

Yes. Apbuild adds a couple of these by default, so you can put app
private libs in one of the directories apbuild adds  (see
http://www.autopackage.org/apbuild-apgcc.php )

> 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.

This is a delicate decision. On one hand, doing it as an install time
check (using 'require') is the proper way to do it. But since QT is
actually a system library, we generally recommend NOT using
autopackage to install it in which case statically linking or
RPATH'ing is the way to go :-)

-Isak

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