I've been digging a bit around this, and I have found a possible cause: 
install.py. It seems to me that the script is installing /_csnd.so 
as a link to /libcsnd.so. This is wrong, because _csnd.so should be a 
binary object built by SWIG. If I'm correct, anyone that uses install.py has a 
broken python interface to csound.


Saludos,
Felipe Sateler

I think this is correct.

Why do we have an install.py script instead of an install target in SConstruct?

Regards,
Mike


On 8/16/09, Felipe Sateler  wrote:
> I've been digging a bit around this, and I have found a possible cause:
> install.py. It seems to me that the script is installing
> /_csnd.so
> as a link to /libcsnd.so. This is wrong, because _csnd.so should be
> a
> binary object built by SWIG. If I'm correct, anyone that uses install.py has
> a
> broken python interface to csound.
>
>
> Saludos,
> Felipe Sateler
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

This goes back years, I had originally done an install target but
Istvan created an install.py script.  I gave up on the install target
after install.py became more featureful and didn't have time to
maintain install target.

On Sun, Aug 16, 2009 at 3:13 PM, Michael Gogins wrote:
> I think this is correct.
>
> Why do we have an install.py script instead of an install target in SConstruct?
>
> Regards,
> Mike
>
>
> On 8/16/09, Felipe Sateler  wrote:
>> I've been digging a bit around this, and I have found a possible cause:
>> install.py. It seems to me that the script is installing
>> /_csnd.so
>> as a link to /libcsnd.so. This is wrong, because _csnd.so should be
>> a
>> binary object built by SWIG. If I'm correct, anyone that uses install.py has
>> a
>> broken python interface to csound.
>>
>>
>> Saludos,
>> Felipe Sateler
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I use the Sconstruct install target in the debian packages. A few things have 
to be manually installed, but this can be easily fixed.

El domingo 16 de agosto, Steven Yi escribió:
> This goes back years, I had originally done an install target but
> Istvan created an install.py script.  I gave up on the install target
> after install.py became more featureful and didn't have time to
> maintain install target.
>
> On Sun, Aug 16, 2009 at 3:13 PM, Michael Gogins 
wrote:
> > I think this is correct.
> >
> > Why do we have an install.py script instead of an install target in
> > SConstruct?
> >
> > Regards,
> > Mike
> >
> > On 8/16/09, Felipe Sateler  wrote:
> >> I've been digging a bit around this, and I have found a possible cause:
> >> install.py. It seems to me that the script is installing
> >> /_csnd.so
> >> as a link to /libcsnd.so. This is wrong, because _csnd.so should
> >> be a
> >> binary object built by SWIG. If I'm correct, anyone that uses install.py
> >> has a
> >> broken python interface to csound.
> >>
> >>
> >> Saludos,
> >> Felipe Sateler
> >
> > --
> > Michael Gogins
> > Irreducible Productions
> > http://www.michael-gogins.com
> > Michael dot Gogins at gmail dot com
> >
> > -------------------------------------------------------------------------
> >----- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> > 30-Day trial. Simplify your report design, integration and deployment -
> > and focus on what you do best, core application coding. Discover what's
> > new with Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ---------------------------------------------------------------------------
>--- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day trial. Simplify your report design, integration and deployment - and
> focus on what you do best, core application coding. Discover what's new
> with Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



Saludos,
Felipe Sateler

El domingo 16 de agosto, Felipe Sateler escribió:
> I've been digging a bit around this, and I have found a possible cause:
> install.py. It seems to me that the script is installing
> /_csnd.so as a link to /libcsnd.so. This is wrong,
> because _csnd.so should be a binary object built by SWIG. If I'm correct,
> anyone that uses install.py has a broken python interface to csound.

On further investigation, the rpm does not seem to suffer from the SONAME 
confusion issue, so fixing install.py should be all that is needed.


Saludos,
Felipe Sateler

That sounds great, Felipe. Could you pass this info to Peter Robinson the
package maintainer?
----- Original Message ----- 
From: "Felipe Sateler" 
To: "Developer discussions" 
Sent: Sunday, August 16, 2009 10:55 PM
Subject: Re: [Cs-dev] csound 5.10 and SoaS


> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 
> 30-Day
> trial. Simplify your report design, integration and deployment - and focus 
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july


--------------------------------------------------------------------------------


> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Unfortunately I cannot even get to build the original package in my Fedora 
virtual machine. _csnd.so is not getting built, and neither is libcsnd.so.5.2 
(although the symlink is created). I get a lot of "command not found" errors 
from scons, I presume the scons version currently in Fedora is broken.

El domingo 16 de agosto, victor escribió:
> That sounds great, Felipe. Could you pass this info to Peter Robinson the
> package maintainer?
> ----- Original Message -----
> From: "Felipe Sateler" 
> To: "Developer discussions" 
> Sent: Sunday, August 16, 2009 10:55 PM
> Subject: Re: [Cs-dev] csound 5.10 and SoaS
>
> > -------------------------------------------------------------------------
> >----- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> > 30-Day
> > trial. Simplify your report design, integration and deployment - and
> > focus on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>
> ---------------------------------------------------------------------------
>-----
>
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ---------------------------------------------------------------------------
>--- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day trial. Simplify your report design, integration and deployment - and
> focus on what you do best, core application coding. Discover what's new
> with Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



Saludos,
Felipe Sateler