Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] format not recognized

Date2007-08-22 04:28
From"Michael Gogins"
SubjectRe: [Cs-dev] format not recognized
OK, thanks for the information, you've obviously learned more about this 
stuff than I have. Which is great, and it helps me try to catch up. I 
_think_ I now understand the difference between:

-- The SONAME, which encodes the version number of the interface.

-- The "real name", which is the name of the actual shared library name, and 
which encodes the version number of the release.

-- The "linker name", which is what dlopen or the OS loader use to open the 
library, and which is created for ldconfig.

The interface version should be the same for both the Csound shared library 
and the Lua interface shared library, and just as I said before, there is no 
real reason that they cannot both be the same file. However, if the SONAMEs 
must differ, then the Lua interface SONAME should be:

liblua5.1-csnd.so.5.1

The real filename should be:

liblua5.1-csnd.so.5.1.6 or maybe liblua5.1.2-csnd.so.5.1.6

And the linker symlink should be:

csnd.so

It is purely a coincidence that the Lua interface version and the Csound 
interface version are both 5.1!

Regards,
Mike

----- Original Message ----- 
From: "Felipe Sateler" 
To: 
Sent: Tuesday, August 21, 2007 8:54 PM
Subject: Re: [Cs-dev] format not recognized


> Michael Gogins wrote:
>
>> SWIG generated wrappers are loaded as plain old "_mymodule.pyd" (Python
>> 2.5) or "_mymodule.so" (earlier versions).
>
> I was actually talking about the lua wrapper. The python wrapper does not
> need a SEVERSION because it is paired with the .py file, and lives
> inside /usr/lib/pythonX.Y/site-packages. This one, according to the Debian
> lua policy should live in /usr/lib, with a symlink in /usr/lib/lua/X.Y/.
> Moreover, the library should be named libluaX.Y-csnd.so.SOVERSION, and 
> only
> the symlink named csnd.so. This is because it allows for different ABI/API
> versions of the library to provide the same module 'csnd'. [1]
>
> Of course, since most of this (installation locations) appears to be
> Debian-specific, there is no need for you (as upstream) to change 
> anything:
> I can change it on the Debian package. However, I would like the SONAME to
> come from you (it would not be nice to break compatibility with other
> distros, should one application link directly to the lua binding). I'm
> guessing that the SOVERSION could, in theory, be the same as the csound
> library: while maybe ABI incompatibility between libcsound versions may 
> not
> actually mean incompatibility of the lua bindings, ABI compatibility
> between libcsound version almost surely means compatibility for the
> wrappers.
>
>> So I think we just need to change the names of the targets to include the
>> version number for the interface shared libraries. I will do this when I
>> refactor the interface shared libraries.
>
> Thanks. However, please wait until I get a definite response/reach a
> consensus with the Debian lua maintainers (should be only a couple of days
> more). It's not nice to change stuff just because Debian wanted to for no
> good reason.
>
> [1] I'm currently talking to the debian lua maintainers about the real 
> need
> of doing this: in our case, the versioning is/could be provided by
> libcsound.
> -- 
>
>  Felipe Sateler
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net