[fpc-pascal] Re: linux: shouldwehard-codeversionedorunversioned shared libraries in our apps?

Graeme Geldenhuys graemeg.lists at gmail.com
Thu Aug 16 16:39:45 CEST 2012


On 16 August 2012 14:39, Marco van de Voort <marcov at stack.nl> wrote:
> Then changing the simple default to libfbclient.so.2 is a problem for
> designtime, since designtime code doesn't even have the emergency
> initializeibase60 workarounds as option. Lazarus will also start to look for
> .2.

I thought this is the FPC mailing list?? Lets not bring the Lazarus
IDE limitations/usage into this discussion. Not everybody here uses
Lazarus IDE, and definitely not the RAD-style dropping components on
forms, and hard-coding field names into your GUI layer.

> Assume that at some point a distro decides to call it .2.1 or something,

Please re-read Jona's earlier reply. There is a set naming standard
for libraries in Linux (yes their does actually seem to be some
standards that distros adhere too). I can confirm what Jonas said. I
searched multiple Firebird client library *.rpm, *.debs and *.txz
packages.  Any Firefbird 2.x client library sets up the .2 and .2.m
where m is the minor version number names. The one thing they DON'T do
is the unversioned name - my issue with FPC, but which will luckily be
fixed soon.

So using your example, there WILL be the following files.

    libfbclient.so.2.1.5        <-  the actual library file
    libfbclient.so.2.1           <- symlink to above  (this does seem optional)
    libfbclient.so.2              <- symblink to above  (always there)

  - Graeme -

fpGUI - a cross-platform Free Pascal GUI toolkit

More information about the fpc-pascal mailing list