troy d. straszheim wrote:
> Brad King wrote:
>> Perhaps the boost CMake code is not setting SOVERSION.
>
> Hmm. It isn't setting it on purpose... If I set either VERSION or
> SOVERSION on a module on the mac, I get:
[snip]
> ../../../lib/libboost_python-mt.1.41.0.dylib -framework Python
> i686-a
Brad King wrote:
If there is no interface version, there is no need for the soname to be
different from the real binary name. IOW, we could just set VERSION=1.2
and no SOVERSION, and CMake will produce
libfoo.so -> libfoo.so.1.2 # link to help static linker -lfoo flags
libfoo.so.1.2
troy d. straszheim wrote:
> Is there some standard buildtime toggle for this, or is
> BUILD_SOVERSIONED okay?
There is no standard AFAIK.
> The option is avaiable on UNIX only.
Note that setting VERSION does set the windows "image version" in DLLs,
but it does not affect the file name.
> The im
Brad King wrote:
Denis Arnaud wrote:
2009/10/28 Vladimir Prus mailto:vladi...@codesourcery.com>>
This might be obvious, but such a soname would be wrong if the above
naming
of libraries is used, since there would be no
libboost_date_time-mt.so.4.
- Volodya
I've just check
