In case anyone cares, I think https://github.com/brucestephens/CMake
contains a quick fix.
On Sat, Feb 20, 2016 at 7:17 PM, Bruce Stephens
wrote:
> Ah, yes. That looks like exactly the bug, thanks.
>
> So it's a straight bug in the ninja generator, not something deliberate
> that I was just fail
Perhaps this bug report fits what you are seeing. Are you seeing this
limitation in the ninja generator?
https://cmake.org/Bug/view.php?id=14140
Clint
On Feb 20, 2016 11:49 AM, Bruce Stephens wrote:
>
> By the looks of it setting the SOVERSION when generating a SHARED library
> creates the s
Ah, yes. That looks like exactly the bug, thanks.
So it's a straight bug in the ninja generator, not something deliberate
that I was just failing to understand. And with the Unix Makefile generator
the compatibility version is set (presumably the current version would be
set if I used VERSION).
O
By the looks of it setting the SOVERSION when generating a SHARED library
creates the symbolic link, but it doesn't seem to use the -current_version
or -compatibility_version flags when linking.
Those flags are set as variables CMAKE_C_OSX_CURRENT_VERSION_FLAG and
CMAKE_C_OSX_COMPATIBILITY_VERSION
