[Interest] Hiding a shared lib? Linux of course.

[Rainer Wiesenfarth]

Am 05.07.2013 08:59, schrieb Till Oliver Knoll:
> [...]
> If the whole purpose was to deploy a given application on Linux (rather
> than, say, compile Qt 5  and install it under /usr/lib "for general
> use"), then
>
> A) I could compile Qt myself (-> make sure that no existing system
> plugins from e.g. KDE are pulled in, which on their turn could pull in
> an older/different Qt version)
>
> B) Deploy that Qt compile with my application
> (/opt/MyApp/[bin|lib|resources|...] - or wherever would be the
> appropriate location for "application bundles" on Linux these days)
>
> [...]
> That should work on Linux, too - right?

It does - almost. At least for Qt 4.x you had to configure your 
"personal" Qt with "-buildkey ..." to avoid base library version 
conflicts with automatically loaded system plugins (your app / your Qt 
.so files(?) automatically load system plugins which in turn want to 
load Qt .so files of a different version or configuration).

I do not know if this still is required for Qt 5.

Best Regards / Mit freundlichen Grüßen
Rainer Wiesenfarth

-- 
Software Engineer | Trimble Imaging Division
Rotebühlstraße 81 | 70178 Stuttgart | Germany
Office +49 711 22881 0 | Fax +49 711 22881 11
http://www.trimble.com/imaging/ | http://www.inpho.de/

Trimble Germany GmbH, Am Prime Parc 11, 65479 Raunheim
Eingetragen beim Amtsgericht Darmstadt unter HRB 83893,
Geschäftsführer: Dr. Frank Heimberg, Hans-Jürgen Gebauer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4495 bytes
Desc: S/MIME Kryptografische Unterschrift
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20130705/26d0066d/attachment.bin>