Closed josch closed 6 years ago
AFAICT, the so version is set already on master. Could you please recheck or explain in more detail what is wrong with the current Cmake code?
Indeed I messed up and you already implemented this. Closing. Thanks!
But do you thus plan to just bump the SOVERSION with every release you make? Even for releases that are backwards compatible?
Will do, although since the move to github no releases have been done so far and unless somebody actively requests a new release I'm not sure I'm going to bother anymore...
Since we have the package in Debian now, I would very much appreciate a release. :)
It would allow us to carry less patches.
Hi,
when building the shared library of orocos-bfl, would you consider setting and maintaining the SOVERSION of the library? The following patch achieves this:
By maintaining the version properly every time you do a release which does or doesn't break ABI backwords compatibility, it is possible for applications to know which version of the library they can use depending on against which version they were linked against.