Re: glibc warnings
"Taj Morton" <[email protected]>
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
On Nov 28, 2007 2:07 AM, Isak Savo <[email protected]> wrote: > 2007/11/28, Justin Karneges <[email protected]>: > > Hi, > > > > I'm trying to build all of our deps with apbuild (openssl, zlib, Qt4), and > > I've mostly succeeded. I can makepackage a test application using QtCore and > > it succeeds without warnings. However, when I use QtGui, then I'm given > > this: > > Do you really need to ship Qt? I think it is better to link > dynamically to QT and use whatever version the user already has on his > system. That way this problem will go away. > zlib is also a system library that all users already have (gzip > depends on it, and so does a lot of other base tools). No need to > build and ship it - just link dynamically. Qt4 should still be shipped/statically linked as it's still uncommon. This will change when KDE 4 comes out, but for now, I think shipping it is the best approach. When I was packaging a Qt 4 app, I ended up building a custom Qt with apgcc. It's not that hard to do--edit the linux-g++ mkspec from the source tarball and change all the "g++"s to "apg++", and all the "gcc"s to "apgcc"s. I'm pretty sure that using an apbuild compiled version of Qt got rid of the errors for me. > OpenSSL is bad to ship because it is a security library and if you > ship it, the user won't benefit from the system upgrades. Most distros have it, no? -Taj -- Taj http://www.wildgardenseed.com/Taj/blog Need a GMail invite? Email me. Peace cannot be kept by force; it can only be achieved by understanding. -- A. Einstein --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]