On 15/09/10 00:46, Claudio Bantaloukas wrote:
> Hi, I recently saw that there's a new cmake based version on git and
> wanted to add my 2$
>
> First of all thanks! I can't wait to start using it :)
>
> I'll give it a shot soon on aix and hp-sux
Claudio,
Great, thanks in advance for testing!
> On Tue, Sep 14, 2010 at 9:45 PM, Julian Taylor wrote:
>> The automatic schema on the other hand has the drawback that api changes
>> must increase the minor number even when they only fix a bug and you
>> unnecessarily increase the library version even when you know you don't
>> need to.
>
> KDE for example uses the first number for source compatibility, the
> second for binary compatibility and the third for bug-fixes. Would it be
> too hard to follow a similar model?
>
> I found the following method for setting version and soversion on
> dynlibs by looking around
>
> set(ABI_VERSION "${MAJOR_VERSION}.${MINOR_VERSION}")
> set(VERSION_STRING
> "${MAJOR_VERSION}.${MINOR_VERSION}-r${LIB_REVISION}")
That's exactly the idea I'd be keen to apply to SOCI.
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
