[Development] Pending decisions on co-installation

Jan Kundrát jkt at flaska.net
Wed Oct 31 13:26:09 CET 2012


On 10/31/12 12:23, Oswald Buddenhagen wrote:
> renaming is unnecessary:
> - there is no problem at all at run-time
> - the problem at build time is solved by -L flags. there is no need for
>   an unversioned symlink in /usr/lib.

On RHEL6, this is how it looks right now:

kundratj at noe2 ~ $ locate /libQtCore.so
/usr/lib64/libQtCore.so.4
/usr/lib64/libQtCore.so.4.6
/usr/lib64/libQtCore.so.4.6.2

kundratj at noe2 ~ $ rpm -qf /usr/lib64/libQtCore.so.4
qt-4.6.2-24.el6.x86_64

If I remember correctly, it's rather hard to persuade the linker to
ignore stuff below /usr/lib64 and use some other destination instead. I
tend to purge such unpleasant memories from my mind, though, so I cannot
provide much detail.

I suspect that RHEL6 would be on the top of the list of Linux
distributions to support.

> renaming is a bit disruptive:
> - projects not done with qmake need adjustment/ifdefs
>   - but then, they probably need adjustment anyway due to the
> libraries
>     having been split, etc.

I can imagine that updating a few lines in a project's build system to
make it link against a different library name would be the smallest
obstacle of any porting process, especially compared to other changes
required. Again, I might be wrong.

Cheers,
Jan

-- 
Trojita, a fast e-mail client -- http://trojita.flaska.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121031/7e3dcb0a/attachment.sig>


More information about the Development mailing list