The symlink exists because the build rules want to make a shared library 
with C stubs for a Python extension module named (using the normal Linux 
naming convention for shared libraries) as lib_modulename.so, whereas Python 
only wants to load a shared library named as _modulename.so. For Python, 
extension module mymodule must have its C stubs in a loadable module (on 
Linux) or DLL (on Windows) named _mymodule.so (on Linux) or .pyd (on 
Windows).

The SConstruct build rules could perhaps be changed on Linux to directly 
create the Python extension module libraries with the names that Python 
expects, using the SHLIBPREFIX flag (this is what happens on Windows). But 
perhaps the SConstruct rule creates the symlink automatically, I do not 
know.

Regards,
Mike

----- Original Message ----- 
From: "Felipe Sateler" 
To: "Michael Gogins" ; "Developer discussions" 

Sent: Wednesday, October 17, 2007 7:11 PM
Subject: Re: [Cs-dev] Csound front page at SF and FAQ


> -------------------------------------------------------------------------
> 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