On 28/09/10 00:19, Mateusz Loskot wrote:
> On 27/09/10 21:29, Mateusz Loskot wrote:
>> On 15/09/10 00:46, Claudio Bantaloukas wrote:
>>> 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}")
>>>
>>> if(WIN32)
>>> set_target_properties( ${LIBRARY_NAME} PROPERTIES
>>> OUTPUT_NAME "${LIBRARY_NAME}.${ABI_VERSION}"
>>> VERSION ${VERSION_STRING})
>>> else()
>>> set_target_properties( ${LIBRARY_NAME} PROPERTIES
>>> OUTPUT_NAME "${LIBRARY_NAME}"
>>> VERSION ${VERSION_STRING}
>>> SOVERSION ${ABI_VERSION} )
>>> endif()
>>>
>>> on windows systems this creates dlls with the abi version built in the
>>> filename, while on unix systems it uses the usual symlink method.
>>
>> I have just committed changes setting the target properties
>> according to the scheme above.
>>
>> I'm going to test on Windows soonly.
>
> Forget about this commit please.
> Apparently, it's rubbish and does not work as expected on Windows.
> I need to apply a few more changes around libraries naming.
>
> Fixes shortly in the repo.
I hope most of this issues related to Windows platform have been fixed.
I'm still testing but SOCI on Windows should be build now.
Testing welcome.
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
