[xmlsec] versioning and library naming policies

Aleksey Sanin aleksey at aleksey.com
Tue Apr 1 11:49:27 PST 2003

Does not work:
    1) after this you need to do " libxmlsec-$(RELEASE)_SOURCES=...."  :)
    2) this breaks linking to libxmlsec.so -> libxmlsec-0.1.so.0.1.1

There is another approach (I've described it in the a separate mail) but 
I don't
like it much. And here is one more option of renaming everything in new 
to "xmlsec1", "libxmlsec1.*, etc. but I don't like it either.
Does having multiple static library version is really a strong 
requirement? If we can
skip it everything lays out perfectly.


John Belmonte wrote:

> Aleksey Sanin wrote:
>> I would be happy to make this stuff seamless for anyone myself and I 
>> have no
>> problems with adding the "-release N.M" option. However, this does 
>> not solve
>>  static libraries problem. They still have no version number at all. 
>> Ideas?
> I don't know much about libtool, but I took a look at how it's done 
> for libgimp.  They just manually set something like the following in 
> Makefile.am:
>     lib_LTLIBRARIES = libxmlsec-$(RELEASE).la
> Thanks,
> -John

More information about the xmlsec mailing list