ome / ome-common-cpp Goto Github PK

Typically a library would change its soname when its ABI changes. However, libome-common is using its version number as soname:

$ objdump -p /usr/local/lib/libome-common.so* | grep SONAME
  SONAME               libome-common.so.5.4.2
  SONAME               libome-common.so.5.4.2

meaning that any library dependent on it would have to be rebuilt and linked again if ome-common is updated. And in terms of debian packaging, that would mean a new binary package name with each single release.

I am unsure about what's policy in ome-common for changing ABI, but if it's when major version changes, then something like commit e9b805b would do it.

cmake's find_package is used to find an installed GTest for the test
suite. However, Google Test itself does not install anymore, and does
not recommend its installation or distribution of pre-built binaries
either. Instead, it recommends each project to compile Google Test.
See their FAQ [why is it not recommended to install a pre-compiled
copy of Google Test for example, into
/usr/local)?

Debian followed upstream recommendation and so there are no gtest
libraries. It seems that instead of find_packages, a project is
supposed to use ExternalProject and then FindGTest. I am guessing
Ubuntu and other Debian derivative projects will have the same issue
running the test suite. I do not know about Fedora and its
derivatives.

In the case of Debian, the headers are available as well as the entire
source tree in '/usr/src' for a project dependent on it for use. See
Debian's README on the
topic