[OE-core] Libs compiled using Yocto has incorrect version appended to their names

[Richard Purdie]

On Thu, 2018-08-16 at 12:42 +0530, Sunny Shukla wrote:
> We are using Rocko build for our am335x starter kit. While building
> core-image-minimal (rootfs) we are facing a strange problem, some of
> the libs we have included are getting build but the version appended
> to libs names are not proper, as shown in the examples below.

In short this is entirely expected. The library version of any given
bit of software doesn't have to match the main recipe/release version
of that piece of software. Taking opkg as an example:

> ls -l ./usr/lib/libopkg.so*
> lrwxrwxrwx 1 root root 16 Aug 9 14:46 ./usr/lib/libopkg.so.1 ->
> libopkg.so.1.0.0
> -rwxr-xr-x 1 root root 143316 Aug 9 14:46 ./usr/lib/libopkg.so.1.0.0
> 
> Here the version number appended after libopkg.so under "./usr/lib/"
> is 1.0.0 instead of 0.3.5 which is the version number of the package
> as described by BB file opkg_0.3.5.bb.

which comes from:

tmp/work/i586-poky-linux/opkg/1_0.3.6-r0/opkg-0.3.6/libopkg/Makefile.am

which sets:

libopkg_la_LDFLAGS = -version-info 1:0:0

hence the library version for libopkg is 1.0.0.

Cheers,

Richard