csnd.py and building from source

[iain duncan]

Hi, I have built csound5.11 from source on linux, and all seems to be
well, but I do not appear to have csnd.py anywhere. Is this not built
unless we build CsoundAC? Or am I just not finding it?

Thanks
Iain



Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

The build options have changed. Look at scons help, or the canned build scripts.

Regards,
Mike

On 10/19/09, Iain Duncan <iainduncan@...> wrote:

> Hi, I have built csound5.11 from source on linux, and all seems to be
> well, but I do not appear to have csnd.py anywhere. Is this not built
> unless we build CsoundAC? Or am I just not finding it?
>
> Thanks
> Iain
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

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


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
> The build options have changed. Look at scons help, or the canned build scripts.

Thanks Mike, I had looked at those, but either I'm not seeing what they
should, or maybe they have not so good names? I see buildInterfaces and
buildPythonWrapper, with the following:

buildInterfaces: Build C++ interface library.

buildPythonWrapper: Set to 1 to build Python wrapper for the C++

But no where in the list do I see the words "Csound API", which is what
I would think most people would be looking for. Are the above the
correct options for building csnd.py? If so, it may be a point worth
clarifying in the building Csound5 page of the manual.

Thanks
Iain

>
> Regards,
> Mike
>
> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> > Hi, I have built csound5.11 from source on linux, and all seems to be
> > well, but I do not appear to have csnd.py anywhere. Is this not built
> > unless we build CsoundAC? Or am I just not finding it?
> >
> > Thanks
> > Iain
> >
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@... with body "unsubscribe
> > csound"
> >
>
>

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
> The build options have changed. Look at scons help, or the canned build scripts.

Hmm, setting buildInterfaces=1 and buildPythonWrappers=1 my build now
fails with the below ( AMD 64, ubuntu 8 ). If anyone can see is wrong,
that would be very helpful.

Thanks
Iain

output from scons :

Generating wrappers...
./H/csound.h:449: Warning(451): Setting a const char * variable may leak
memory.
interfaces/cs_glue.hpp:507: Warning(473): Returning a pointer or
reference in a director method is not recommended.
g++ -o interfaces/python_interface_wrap.os -c -fexceptions -Wno-format
-DGNU_GETTEXT -g -fomit-frame-pointer -freorder-blocks -DLINUX -DPIPES
-fno-strict-aliasing -fno-strict-aliasing -fno-strict-aliasing
-fno-strict-aliasing -fPIC -DHAVE_LIBSNDFILE=1016 -DHAVE_FLTK -DBETA
-DHAVE_SOCKETS -DHAVE_PTHREAD_BARRIER_INIT -DHAVE_SYNC_LOCK_TEST_AND_SET
-DHAVE_FCNTL_H -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H
-DHAVE_SYS_TYPES_H -DHAVE_TERMIOS_H -DHAVE_VALUES_H -DHAVE_SOCKETS
-DHAVE_DIRENT_H -D__BUILDING_LIBCSOUND -D__BUILDING_CSOUND_INTERFACES
-I. -IH -I/usr/include/fltk-1.1 -I/usr/local/include -I/usr/include
-I/usr/include -I/usr/X11R6/include -Iinterfaces
-I/usr/include/python2.5 -I/usr/local/include/python2.5
interfaces/python_interface_wrap.cc
interfaces/python_interface_wrap.cc: In function ‘PyObject*
_wrap_CppSound_pythonMessageCallback(PyObject*, PyObject*)’:
interfaces/python_interface_wrap.cc:35363: error: invalid array
assignment
interfaces/python_interface_wrap.cc: In static member function ‘static
int swig::traits_asptr<std::map<K, T, std::less<_Key>,
std::allocator<std::pair<const _Key, _Tp> > > >::asptr(PyObject*,
std::map<K, T, std::less<_Key>, std::allocator<std::pair<const _Key,
_Tp> > >**) [with K = int, T = std::basic_string<char,
std::char_traits<char>, std::allocator<char> >]’:
interfaces/python_interface_wrap.cc:4250:   instantiated from ‘int
swig::asptr(PyObject*, Type**) [with Type = std::map<int,
std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
std::less<int>, std::allocator<std::pair<const int,
std::basic_string<char, std::char_traits<char>, std::allocator<char> > >
> >]’
interfaces/python_interface_wrap.cc:28508:   instantiated from here
interfaces/python_interface_wrap.cc:5325: warning: deprecated conversion
from string constant to ‘char*’
scons: *** [interfaces/python_interface_wrap.os] Error 1
scons: building terminated because of errors.




Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

There a various APIs, also called interfaces, for different languages.
The libraries and the build system are now factored out by language.
You have to build C++ for all of them, however. All the various
langauge interfaces (or APIs) are "wrappers" around the high-level C++
interface library, which in turn is a wrapper around the low level C++
API and the C API which already exist in the Csound shared library.

Hope this helps,
Mike

On 10/19/09, Iain Duncan <iainduncan@...> wrote:

> On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
>> The build options have changed. Look at scons help, or the canned build
>> scripts.
>
> Thanks Mike, I had looked at those, but either I'm not seeing what they
> should, or maybe they have not so good names? I see buildInterfaces and
> buildPythonWrapper, with the following:
>
> buildInterfaces: Build C++ interface library.
>
> buildPythonWrapper: Set to 1 to build Python wrapper for the C++
>
> But no where in the list do I see the words "Csound API", which is what
> I would think most people would be looking for. Are the above the
> correct options for building csnd.py? If so, it may be a point worth
> clarifying in the building Csound5 page of the manual.
>
> Thanks
> Iain
>
>>
>> Regards,
>> Mike
>>
>> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> > Hi, I have built csound5.11 from source on linux, and all seems to be
>> > well, but I do not appear to have csnd.py anywhere. Is this not built
>> > unless we build CsoundAC? Or am I just not finding it?
>> >
>> > Thanks
>> > Iain
>> >
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@... with body "unsubscribe
>> > csound"
>> >
>>
>>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

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


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

Do a complete cleanup, incuding files generated by SWIG, get the
latest sources, and try again. The Python message callback code
recently changed.

Regards,
Mike

On 10/19/09, Michael Gogins <michael.gogins@...> wrote:

> There a various APIs, also called interfaces, for different languages.
> The libraries and the build system are now factored out by language.
> You have to build C++ for all of them, however. All the various
> langauge interfaces (or APIs) are "wrappers" around the high-level C++
> interface library, which in turn is a wrapper around the low level C++
> API and the C API which already exist in the Csound shared library.
>
> Hope this helps,
> Mike
>
> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
>>> The build options have changed. Look at scons help, or the canned build
>>> scripts.
>>
>> Thanks Mike, I had looked at those, but either I'm not seeing what they
>> should, or maybe they have not so good names? I see buildInterfaces and
>> buildPythonWrapper, with the following:
>>
>> buildInterfaces: Build C++ interface library.
>>
>> buildPythonWrapper: Set to 1 to build Python wrapper for the C++
>>
>> But no where in the list do I see the words "Csound API", which is what
>> I would think most people would be looking for. Are the above the
>> correct options for building csnd.py? If so, it may be a point worth
>> clarifying in the building Csound5 page of the manual.
>>
>> Thanks
>> Iain
>>
>>>
>>> Regards,
>>> Mike
>>>
>>> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>>> > Hi, I have built csound5.11 from source on linux, and all seems to be
>>> > well, but I do not appear to have csnd.py anywhere. Is this not built
>>> > unless we build CsoundAC? Or am I just not finding it?
>>> >
>>> > Thanks
>>> > Iain
>>> >
>>> >
>>> >
>>> > Send bugs reports to this list.
>>> > To unsubscribe, send email sympa@... with body
>>> > "unsubscribe
>>> > csound"
>>> >
>>>
>>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>

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


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Mon, 2009-10-19 at 01:13 -0400, Michael Gogins wrote:
> There a various APIs, also called interfaces, for different languages.
> The libraries and the build system are now factored out by language.
> You have to build C++ for all of them, however. All the various
> langauge interfaces (or APIs) are "wrappers" around the high-level C++
> interface library, which in turn is a wrapper around the low level C++
> API and the C API which already exist in the Csound shared library.
>
> Hope this helps,

It does, thanks. I'm curious as to why we don't have more of that kind
of thing in the current manual on line manual, or did I miss it?

thanks again
Iain

> Mike
>
> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> > On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
> >> The build options have changed. Look at scons help, or the canned build
> >> scripts.
> >
> > Thanks Mike, I had looked at those, but either I'm not seeing what they
> > should, or maybe they have not so good names? I see buildInterfaces and
> > buildPythonWrapper, with the following:
> >
> > buildInterfaces: Build C++ interface library.
> >
> > buildPythonWrapper: Set to 1 to build Python wrapper for the C++
> >
> > But no where in the list do I see the words "Csound API", which is what
> > I would think most people would be looking for. Are the above the
> > correct options for building csnd.py? If so, it may be a point worth
> > clarifying in the building Csound5 page of the manual.
> >
> > Thanks
> > Iain
> >
> >>
> >> Regards,
> >> Mike
> >>
> >> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> >> > Hi, I have built csound5.11 from source on linux, and all seems to be
> >> > well, but I do not appear to have csnd.py anywhere. Is this not built
> >> > unless we build CsoundAC? Or am I just not finding it?
> >> >
> >> > Thanks
> >> > Iain
> >> >
> >> >
> >> >
> >> > Send bugs reports to this list.
> >> > To unsubscribe, send email sympa@... with body "unsubscribe
> >> > csound"
> >> >
> >>
> >>
> >
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@... with body "unsubscribe
> > csound"
> >
>
>

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

It is in the introduction to the API reference.

Regards,
Mike

On 10/19/09, Iain Duncan <iainduncan@...> wrote:

> On Mon, 2009-10-19 at 01:13 -0400, Michael Gogins wrote:
>> There a various APIs, also called interfaces, for different languages.
>> The libraries and the build system are now factored out by language.
>> You have to build C++ for all of them, however. All the various
>> langauge interfaces (or APIs) are "wrappers" around the high-level C++
>> interface library, which in turn is a wrapper around the low level C++
>> API and the C API which already exist in the Csound shared library.
>>
>> Hope this helps,
>
> It does, thanks. I'm curious as to why we don't have more of that kind
> of thing in the current manual on line manual, or did I miss it?
>
> thanks again
> Iain
>
>> Mike
>>
>> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> > On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
>> >> The build options have changed. Look at scons help, or the canned build
>> >> scripts.
>> >
>> > Thanks Mike, I had looked at those, but either I'm not seeing what they
>> > should, or maybe they have not so good names? I see buildInterfaces and
>> > buildPythonWrapper, with the following:
>> >
>> > buildInterfaces: Build C++ interface library.
>> >
>> > buildPythonWrapper: Set to 1 to build Python wrapper for the C++
>> >
>> > But no where in the list do I see the words "Csound API", which is what
>> > I would think most people would be looking for. Are the above the
>> > correct options for building csnd.py? If so, it may be a point worth
>> > clarifying in the building Csound5 page of the manual.
>> >
>> > Thanks
>> > Iain
>> >
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> >> > Hi, I have built csound5.11 from source on linux, and all seems to be
>> >> > well, but I do not appear to have csnd.py anywhere. Is this not built
>> >> > unless we build CsoundAC? Or am I just not finding it?
>> >> >
>> >> > Thanks
>> >> > Iain
>> >> >
>> >> >
>> >> >
>> >> > Send bugs reports to this list.
>> >> > To unsubscribe, send email sympa@... with body
>> >> > "unsubscribe
>> >> > csound"
>> >> >
>> >>
>> >>
>> >
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@... with body "unsubscribe
>> > csound"
>> >
>>
>>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

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


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Victor Lazzarini]

This sounds like a SWIG wrapping problem for 64bit OSs that I think has been
fixed in CVS.

Victor
----- Original Message -----
From: "Iain Duncan" <iainduncan@...>
To: <csound@...>
Sent: Monday, October 19, 2009 6:12 AM
Subject: [Csnd] Re: Re: csnd.py and building from source


On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
> The build options have changed. Look at scons help, or the canned build
> scripts.

Hmm, setting buildInterfaces=1 and buildPythonWrappers=1 my build now
fails with the below ( AMD 64, ubuntu 8 ). If anyone can see is wrong,
that would be very helpful.

Thanks
Iain

output from scons :

Generating wrappers...
./H/csound.h:449: Warning(451): Setting a const char * variable may leak
memory.
interfaces/cs_glue.hpp:507: Warning(473): Returning a pointer or
reference in a director method is not recommended.
g++ -o interfaces/python_interface_wrap.os -c -fexceptions -Wno-format
-DGNU_GETTEXT -g -fomit-frame-pointer -freorder-blocks -DLINUX -DPIPES
-fno-strict-aliasing -fno-strict-aliasing -fno-strict-aliasing
-fno-strict-aliasing -fPIC -DHAVE_LIBSNDFILE=1016 -DHAVE_FLTK -DBETA
-DHAVE_SOCKETS -DHAVE_PTHREAD_BARRIER_INIT -DHAVE_SYNC_LOCK_TEST_AND_SET
-DHAVE_FCNTL_H -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H
-DHAVE_SYS_TYPES_H -DHAVE_TERMIOS_H -DHAVE_VALUES_H -DHAVE_SOCKETS
-DHAVE_DIRENT_H -D__BUILDING_LIBCSOUND -D__BUILDING_CSOUND_INTERFACES
-I. -IH -I/usr/include/fltk-1.1 -I/usr/local/include -I/usr/include
-I/usr/include -I/usr/X11R6/include -Iinterfaces
-I/usr/include/python2.5 -I/usr/local/include/python2.5
interfaces/python_interface_wrap.cc
interfaces/python_interface_wrap.cc: In function ‘PyObject*
_wrap_CppSound_pythonMessageCallback(PyObject*, PyObject*)’:
interfaces/python_interface_wrap.cc:35363: error: invalid array
assignment
interfaces/python_interface_wrap.cc: In static member function ‘static
int swig::traits_asptr<std::map<K, T, std::less<_Key>,
std::allocator<std::pair<const _Key, _Tp> > > >::asptr(PyObject*,
std::map<K, T, std::less<_Key>, std::allocator<std::pair<const _Key,
_Tp> > >**) [with K = int, T = std::basic_string<char,
std::char_traits<char>, std::allocator<char> >]’:
interfaces/python_interface_wrap.cc:4250:   instantiated from ‘int
swig::asptr(PyObject*, Type**) [with Type = std::map<int,
std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
std::less<int>, std::allocator<std::pair<const int,
std::basic_string<char, std::char_traits<char>, std::allocator<char> > >
> >]’
interfaces/python_interface_wrap.cc:28508:   instantiated from here
interfaces/python_interface_wrap.cc:5325: warning: deprecated conversion
from string constant to ‘char*’
scons: *** [interfaces/python_interface_wrap.os] Error 1
scons: building terminated because of errors.




Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe
csound"=



Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Mon, 2009-10-19 at 08:23 +0100, victor wrote:
> This sounds like a SWIG wrapping problem for 64bit OSs that I think has been
> fixed in CVS.

Seems to have done the job!  Or at least, it compiles. ;-)

Thanks
Iain

>
> Victor
> ----- Original Message -----
> From: "Iain Duncan" <iainduncan@...>
> To: <csound@...>
> Sent: Monday, October 19, 2009 6:12 AM
> Subject: [Csnd] Re: Re: csnd.py and building from source
>
>
> On Mon, 2009-10-19 at 00:56 -0400, Michael Gogins wrote:
> > The build options have changed. Look at scons help, or the canned build
> > scripts.
>
> Hmm, setting buildInterfaces=1 and buildPythonWrappers=1 my build now
> fails with the below ( AMD 64, ubuntu 8 ). If anyone can see is wrong,
> that would be very helpful.
>
> Thanks
> Iain
>
> output from scons :
>
> Generating wrappers...
> ./H/csound.h:449: Warning(451): Setting a const char * variable may leak
> memory.
> interfaces/cs_glue.hpp:507: Warning(473): Returning a pointer or
> reference in a director method is not recommended.
> g++ -o interfaces/python_interface_wrap.os -c -fexceptions -Wno-format
> -DGNU_GETTEXT -g -fomit-frame-pointer -freorder-blocks -DLINUX -DPIPES
> -fno-strict-aliasing -fno-strict-aliasing -fno-strict-aliasing
> -fno-strict-aliasing -fPIC -DHAVE_LIBSNDFILE=1016 -DHAVE_FLTK -DBETA
> -DHAVE_SOCKETS -DHAVE_PTHREAD_BARRIER_INIT -DHAVE_SYNC_LOCK_TEST_AND_SET
> -DHAVE_FCNTL_H -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H
> -DHAVE_SYS_TYPES_H -DHAVE_TERMIOS_H -DHAVE_VALUES_H -DHAVE_SOCKETS
> -DHAVE_DIRENT_H -D__BUILDING_LIBCSOUND -D__BUILDING_CSOUND_INTERFACES
> -I. -IH -I/usr/include/fltk-1.1 -I/usr/local/include -I/usr/include
> -I/usr/include -I/usr/X11R6/include -Iinterfaces
> -I/usr/include/python2.5 -I/usr/local/include/python2.5
> interfaces/python_interface_wrap.cc
> interfaces/python_interface_wrap.cc: In function ‘PyObject*
> _wrap_CppSound_pythonMessageCallback(PyObject*, PyObject*)’:
> interfaces/python_interface_wrap.cc:35363: error: invalid array
> assignment
> interfaces/python_interface_wrap.cc: In static member function ‘static
> int swig::traits_asptr<std::map<K, T, std::less<_Key>,
> std::allocator<std::pair<const _Key, _Tp> > > >::asptr(PyObject*,
> std::map<K, T, std::less<_Key>, std::allocator<std::pair<const _Key,
> _Tp> > >**) [with K = int, T = std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >]’:
> interfaces/python_interface_wrap.cc:4250:   instantiated from ‘int
> swig::asptr(PyObject*, Type**) [with Type = std::map<int,
> std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
> std::less<int>, std::allocator<std::pair<const int,
> std::basic_string<char, std::char_traits<char>, std::allocator<char> > >
> > >]’
> interfaces/python_interface_wrap.cc:28508:   instantiated from here
> interfaces/python_interface_wrap.cc:5325: warning: deprecated conversion
> from string constant to ‘char*’
> scons: *** [interfaces/python_interface_wrap.os] Error 1
> scons: building terminated because of errors.
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"=
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"