library version uses wrong flag for C++, not C

[kyngchaos]

The internal library version on OSX comes out as 0.0.0 for the C++ libgeos. libgoes_c does have the library version. The file names do have the version for both. That is, using otool -L:

/usr/local/lib/libgeos.3.0.0.dylib (compatibility version 0.0.0, current version 0.0.0)

/usr/local/lib/libgeos_c.1.4.1.dylib (compatibility version 6.0.0, current version 6.1.0)

I see that in the Makefile for the C library there is:

libgeos_c_la_LDFLAGS = \
	-version-info 5:1:4 \
	-no-undefined

while the C++ Makefile has:

libgeos_la_LDFLAGS = \
	-release 3.0.0 \
	-no-undefined

Libtool seems to be ignoring the -release flag and using the default 0:0:0.

[mloskot]

William,

I'm not sure about the background, perhaps Sandro intentionally removed it from the C API library.

Would you have any suggestion for the -release value?

[pramsey]

If you look at the docs on version-info here ​http://www.gnu.org/software/libtool/manual/libtool.html you'll see the explanation: we support binary compatibility for capi only. Everything else breaks binary compatibility across releases, even minor ones.

[(none)]

Milestone 3.1.0 deleted