On 12/09/10 03:35, Julian Taylor wrote:
> On Sun, 2010-09-12 at 02:24 +0200, Mateusz Loskot wrote:
>>
>> FYI, I have dropped the naming covention used in previous SOCI versions
>> and based on Boost concept using indicators of debug/release,
>> single/multi-thread, etc.
>>
>> CMake config simply generates libsoci_core, libsoci_sqlite2, etc.
>
> This creates libraries conforming to debian policy (and probably also to
> that of most other linux distributions) [1,2,3]:
> set_target_properties(${SOCI_CORE_TARGET}
> PROPERTIES
> SOVERSION ${SOCI_API_VERSION}
> VERSION ${SOCI_VERSION})
> SOVERSION should be incremented on every ABI/API change. It is
> used for the SONAME ELF property and symbolic links.
> VERSION can be the current version number, it is used for the actual
> library name.
Julian,
Thanks for the SOVERSION updates.
I have added soci_version() macro that takes care of setting
SOCI_VERSION string as well as SOCI_SOVERSION.
I have decided to go for simple approach:
SOCI_VERSION = MAJOR.MINOR.PATCH
SOCI_SOVERSION = MAJOR
This scheme is a proposal and can be changed.
Thinking of API/ABI versioning and given amount of changes that have
happened in SOCI, I've started to think that the upcoming
release should be numbered 4.0.0 rather than 3.1.0.
Then, the simple approach of bumping SOVERSION according to MAJOR
version number could be cultivated in future releases.
What you think?
And you Maciej?
> I have no idea how this is handled in windows, but I guess cmake should
> be able to get it right there too.
I'm not sure either.
I remember that with older versions of CMake, popular approach was to
manually manipulate DLL name (e.g. libsoci_core-SOVERSION.dll)
http://www.cmake.org/pipermail/cmake/2009-October/032511.html
Perhaps it is handled now natively by CMake 2.8+, but I will check later.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
