Hi Julian and all,

This thread is a little bit old, but I'm currently facing the same problem,
i.e. trying to compile csound on 10.6. In practice the main problem is that
fltk 1.10 cannot be compiled in x86_64 because it still relies on Carbon.
The latest development release of fltk 1.3.x is compiling in 64 bits, since
it relies on Cocoa, but then, the problem is that the compilation of csound
fails, exactly for this reason: it seems to ask for Cocoa libs that are not
defined in the building script.

So my question is: how did you succeed ?

Any help would be greatly appreciated !

Alexis Baskind


Julian Peterson-4 wrote:
> 
> Yes, it is a 64 bit os.  Csound seems to be running w/o issue, but  
> I've had to build nearly everything from scratch since few installers  
> include x86-64 along with i386 and ppc in the mac binaries.  For  
> example, currently csoundapi~ is broken for me because csoundapi is  
> compiled 64 bit but my version of pd is not... no fault of csound, of  
> course.
> 
> JP
> 
> 
> 
> On Oct 27, 2009, at 10:47 AM, victor wrote:
> 
>> Since 10.6 is possibly a 64bit OS (?), it will be interesting to see  
>> if no
>> issues arise
>> (I expect none).
>>
>> I am glad the csmodule.c issue got solved, it bothered me to see those
>> deprecated
>> messages; and the solution was the simplest: use the POSIX code!
>>
>> Victor
>> ----- Original Message -----
>> From: "Julian Peterson" 
>> To: "Developer discussions" 
>> Sent: Tuesday, October 27, 2009 1:00 AM
>> Subject: Re: [Cs-dev] building on osx 10.6
>>
>>
>>> Wonderful!  Thanks so much for looking into it.
>>>
>>> I've now successfully build csound on 10.6.  The only change I made
>>> was to SConstruct, line 609:
>>>
>>> OSXSystemPythonVersions = { 0:0, 1:0, 2:2, 3:3, 4:3, 5:5, 6:6 }
>>>
>>> (appended 6:6 at the end, SnowLeopard ships with pythons 4,5, and 6).
>>>
>>>
>>>
>>> Thanks again Victor.
>>>
>>> J
>>>
>>>
>>>
>>> On Oct 26, 2009, at 2:00 PM, Victor Lazzarini wrote:
>>>
>>>> I mean solution 2, use dlopen().
>>>>
>>>> Victor
>>>> On 26 Oct 2009, at 20:05, Victor Lazzarini wrote:
>>>>
>>>>> That works, so that's what you should do.
>>>>> I have updated CVS with these changes and you can check them out.
>>>>>
>>>>> Victor
>>>>>
>>>>>
>>>>> On 26 Oct 2009, at 19:50, Victor Lazzarini wrote:
>>>>>
>>>>>> Two solutions:
>>>>>> 1) add /usr/lib/dylib1.10.5.o to the list of objects to be linked.
>>>>>> It's a hack, but
>>>>>>    might work.
>>>>>>
>>>>>> 2) OSX actually supports dlopen() so you can try commenting out
>>>>>> all the
>>>>>> Mac specific code in csmodule.c and use the LINUX one (by changing
>>>>>> the
>>>>>> ifdefs around). I'll actually test this later on OSX 10.5
>>>>>>
>>>>>> Victor
>>>>>>
>>>>>> On 26 Oct 2009, at 19:41, Julian Peterson wrote:
>>>>>>
>>>>>>> Also, I get the same output regarding usr/lib/dylib1.10.5.o:
>>>>>>>
>>>>>>> subotnick:csound5 julianp$ nm -a  /usr/lib/dylib1.10.5.o
>>>>>>>      U ___dso_handle
>>>>>>> 00000024 T __dyld_func_lookup
>>>>>>> 0000003c d dyld__mach_header
>>>>>>> 00000000 T dyld_stub_binding_helper
>>>>>>>
>>>>>>>
>>>>>>> So it looks like the function still exists, but is not found?   
>>>>>>> This
>>>>>>> water's a bit too deep for me.... might have to give up for the
>>>>>>> time
>>>>>>> being.
>>>>>>>
>>>>>>> J
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Oct 26, 2009, at 11:02 AM, Victor Lazzarini wrote:
>>>>>>>
>>>>>>>> This is the plugin loading module. It looks like
>>>>>>>> _dyld_func_lookup()
>>>>>>>> is not
>>>>>>>> found in 10.6 (possibly?).
>>>>>>>>
>>>>>>>> On OSX10.5, this function is part of the system as seen in:
>>>>>>>>
>>>>>>>> coltrane:csound5-float victor$
>>>>>>>> 00000014 T __dyld_func_lookup
>>>>>>>>     U __mh_dylib_header
>>>>>>>> 00000024 d dyld__mach_header
>>>>>>>> 00000000 T dyld_stub_binding_helper
>>>>>>>>
>>>>>>>> I have been having deprecated messages about other functions in
>>>>>>>> that
>>>>>>>> file, but not that particular one.
>>>>>>>>
>>>>>>>> Try this modification in csmodule.c
>>>>>>>>
>>>>>>>>    _dyld_func_lookup("__dyld_NSMakePrivateModulePublic",
>>>>>>>>                      (void **) &make_private_module_public);
>>>>>>>>
>>>>>>>> The 2nd argument has the wrong type. But that should not make  
>>>>>>>> the
>>>>>>>> symbol undefined.
>>>>>>>>
>>>>>>>> Victor
>>>>>>>>
>>>>>>>> On 26 Oct 2009, at 17:17, Julian Peterson wrote:
>>>>>>>>
>>>>>>>>> Hello Victor and all.
>>>>>>>>>
>>>>>>>>> I'm trying to build the latest csound (cvs) on osx10.6.  I've
>>>>>>>>> reached
>>>>>>>>> an impasse, which is the following error:
>>>>>>>>>
>>>>>>>>> Undefined symbols:
>>>>>>>>> "__dyld_func_lookup", referenced from:
>>>>>>>>> _csoundOpenLibrary in csmodule.os
>>>>>>>>> ld: symbol(s) not found
>>>>>>>>> collect2: ld returned 1 exit status
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Have any ideas about how to fix this?
>>>>>>>>>
>>>>>>>>> I'll report back on the changes I've had to make to get it all
>>>>>>>>> built,
>>>>>>>>> once I get there.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> JP
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>>>>> SF,
>>>>>>>>> CA
>>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>>> Jumpstart
>>>>>>>>> your
>>>>>>>>> developing skills, take BlackBerry mobile applications to  
>>>>>>>>> market
>>>>>>>>> and
>>>>>>>>> stay
>>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.  
>>>>>>>>> Register
>>>>>>>>> now!
>>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>>> _______________________________________________
>>>>>>>>> Csound-devel mailing list
>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>>>> SF,
>>>>>>>> CA
>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>> Jumpstart
>>>>>>>> your
>>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>>> and
>>>>>>>> stay
>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>>> now!
>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>>> CA
>>>>>>> is the only developer event you need to attend this year.  
>>>>>>> Jumpstart
>>>>>>> your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and
>>>>>>> stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>> SF, CA
>>>>>> is the only developer event you need to attend this year.  
>>>>>> Jumpstart
>>>>>> your
>>>>>> developing skills, take BlackBerry mobile applications to market  
>>>>>> and
>>>>>> stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>>> CA
>>>>> is the only developer event you need to attend this year. Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market  
>>>>> and
>>>>> stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market and
>>>> stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart  
>>> your
>>> developing skills, take BlackBerry mobile applications to market  
>>> and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market and  
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/building-on-osx-10.6-tp26063774p28612138.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The absence of a C API for GUIs on OSX 10.6 is a major PITA. Why do  
they do this?

Victor
On 19 May 2010, at 21:21, Alexis Baskind wrote:

>
> Hi Julian and all,
>
> This thread is a little bit old, but I'm currently facing the same  
> problem,
> i.e. trying to compile csound on 10.6. In practice the main problem  
> is that
> fltk 1.10 cannot be compiled in x86_64 because it still relies on  
> Carbon.
> The latest development release of fltk 1.3.x is compiling in 64  
> bits, since
> it relies on Cocoa, but then, the problem is that the compilation of  
> csound
> fails, exactly for this reason: it seems to ask for Cocoa libs that  
> are not
> defined in the building script.
>
> So my question is: how did you succeed ?
>
> Any help would be greatly appreciated !
>
> Alexis Baskind
>
>
> Julian Peterson-4 wrote:
>>
>> Yes, it is a 64 bit os.  Csound seems to be running w/o issue, but
>> I've had to build nearly everything from scratch since few installers
>> include x86-64 along with i386 and ppc in the mac binaries.  For
>> example, currently csoundapi~ is broken for me because csoundapi is
>> compiled 64 bit but my version of pd is not... no fault of csound, of
>> course.
>>
>> JP
>>
>>
>>
>> On Oct 27, 2009, at 10:47 AM, victor wrote:
>>
>>> Since 10.6 is possibly a 64bit OS (?), it will be interesting to see
>>> if no
>>> issues arise
>>> (I expect none).
>>>
>>> I am glad the csmodule.c issue got solved, it bothered me to see  
>>> those
>>> deprecated
>>> messages; and the solution was the simplest: use the POSIX code!
>>>
>>> Victor
>>> ----- Original Message -----
>>> From: "Julian Peterson" 
>>> To: "Developer discussions" 
>>> Sent: Tuesday, October 27, 2009 1:00 AM
>>> Subject: Re: [Cs-dev] building on osx 10.6
>>>
>>>
>>>> Wonderful!  Thanks so much for looking into it.
>>>>
>>>> I've now successfully build csound on 10.6.  The only change I made
>>>> was to SConstruct, line 609:
>>>>
>>>> OSXSystemPythonVersions = { 0:0, 1:0, 2:2, 3:3, 4:3, 5:5, 6:6 }
>>>>
>>>> (appended 6:6 at the end, SnowLeopard ships with pythons 4,5, and  
>>>> 6).
>>>>
>>>>
>>>>
>>>> Thanks again Victor.
>>>>
>>>> J
>>>>
>>>>
>>>>
>>>> On Oct 26, 2009, at 2:00 PM, Victor Lazzarini wrote:
>>>>
>>>>> I mean solution 2, use dlopen().
>>>>>
>>>>> Victor
>>>>> On 26 Oct 2009, at 20:05, Victor Lazzarini wrote:
>>>>>
>>>>>> That works, so that's what you should do.
>>>>>> I have updated CVS with these changes and you can check them out.
>>>>>>
>>>>>> Victor
>>>>>>
>>>>>>
>>>>>> On 26 Oct 2009, at 19:50, Victor Lazzarini wrote:
>>>>>>
>>>>>>> Two solutions:
>>>>>>> 1) add /usr/lib/dylib1.10.5.o to the list of objects to be  
>>>>>>> linked.
>>>>>>> It's a hack, but
>>>>>>>   might work.
>>>>>>>
>>>>>>> 2) OSX actually supports dlopen() so you can try commenting out
>>>>>>> all the
>>>>>>> Mac specific code in csmodule.c and use the LINUX one (by  
>>>>>>> changing
>>>>>>> the
>>>>>>> ifdefs around). I'll actually test this later on OSX 10.5
>>>>>>>
>>>>>>> Victor
>>>>>>>
>>>>>>> On 26 Oct 2009, at 19:41, Julian Peterson wrote:
>>>>>>>
>>>>>>>> Also, I get the same output regarding usr/lib/dylib1.10.5.o:
>>>>>>>>
>>>>>>>> subotnick:csound5 julianp$ nm -a  /usr/lib/dylib1.10.5.o
>>>>>>>>     U ___dso_handle
>>>>>>>> 00000024 T __dyld_func_lookup
>>>>>>>> 0000003c d dyld__mach_header
>>>>>>>> 00000000 T dyld_stub_binding_helper
>>>>>>>>
>>>>>>>>
>>>>>>>> So it looks like the function still exists, but is not found?
>>>>>>>> This
>>>>>>>> water's a bit too deep for me.... might have to give up for the
>>>>>>>> time
>>>>>>>> being.
>>>>>>>>
>>>>>>>> J
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Oct 26, 2009, at 11:02 AM, Victor Lazzarini wrote:
>>>>>>>>
>>>>>>>>> This is the plugin loading module. It looks like
>>>>>>>>> _dyld_func_lookup()
>>>>>>>>> is not
>>>>>>>>> found in 10.6 (possibly?).
>>>>>>>>>
>>>>>>>>> On OSX10.5, this function is part of the system as seen in:
>>>>>>>>>
>>>>>>>>> coltrane:csound5-float victor$
>>>>>>>>> 00000014 T __dyld_func_lookup
>>>>>>>>>    U __mh_dylib_header
>>>>>>>>> 00000024 d dyld__mach_header
>>>>>>>>> 00000000 T dyld_stub_binding_helper
>>>>>>>>>
>>>>>>>>> I have been having deprecated messages about other functions  
>>>>>>>>> in
>>>>>>>>> that
>>>>>>>>> file, but not that particular one.
>>>>>>>>>
>>>>>>>>> Try this modification in csmodule.c
>>>>>>>>>
>>>>>>>>>   _dyld_func_lookup("__dyld_NSMakePrivateModulePublic",
>>>>>>>>>                     (void **) &make_private_module_public);
>>>>>>>>>
>>>>>>>>> The 2nd argument has the wrong type. But that should not make
>>>>>>>>> the
>>>>>>>>> symbol undefined.
>>>>>>>>>
>>>>>>>>> Victor
>>>>>>>>>
>>>>>>>>> On 26 Oct 2009, at 17:17, Julian Peterson wrote:
>>>>>>>>>
>>>>>>>>>> Hello Victor and all.
>>>>>>>>>>
>>>>>>>>>> I'm trying to build the latest csound (cvs) on osx10.6.  I've
>>>>>>>>>> reached
>>>>>>>>>> an impasse, which is the following error:
>>>>>>>>>>
>>>>>>>>>> Undefined symbols:
>>>>>>>>>> "__dyld_func_lookup", referenced from:
>>>>>>>>>> _csoundOpenLibrary in csmodule.os
>>>>>>>>>> ld: symbol(s) not found
>>>>>>>>>> collect2: ld returned 1 exit status
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Have any ideas about how to fix this?
>>>>>>>>>>
>>>>>>>>>> I'll report back on the changes I've had to make to get it  
>>>>>>>>>> all
>>>>>>>>>> built,
>>>>>>>>>> once I get there.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> JP
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>>>>> SF,
>>>>>>>>>> CA
>>>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>>>> Jumpstart
>>>>>>>>>> your
>>>>>>>>>> developing skills, take BlackBerry mobile applications to
>>>>>>>>>> market
>>>>>>>>>> and
>>>>>>>>>> stay
>>>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.
>>>>>>>>>> Register
>>>>>>>>>> now!
>>>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Csound-devel mailing list
>>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>>>> SF,
>>>>>>>>> CA
>>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>>> Jumpstart
>>>>>>>>> your
>>>>>>>>> developing skills, take BlackBerry mobile applications to  
>>>>>>>>> market
>>>>>>>>> and
>>>>>>>>> stay
>>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.  
>>>>>>>>> Register
>>>>>>>>> now!
>>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>>> _______________________________________________
>>>>>>>>> Csound-devel mailing list
>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>>>>> SF,
>>>>>>>> CA
>>>>>>>> is the only developer event you need to attend this year.
>>>>>>>> Jumpstart
>>>>>>>> your
>>>>>>>> developing skills, take BlackBerry mobile applications to  
>>>>>>>> market
>>>>>>>> and
>>>>>>>> stay
>>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009.  
>>>>>>>> Register
>>>>>>>> now!
>>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
>>>>>>> SF, CA
>>>>>>> is the only developer event you need to attend this year.
>>>>>>> Jumpstart
>>>>>>> your
>>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>>> and
>>>>>>> stay
>>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>>> now!
>>>>>>> http://p.sf.net/sfu/devconference
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
>>>>>> CA
>>>>>> is the only developer event you need to attend this year.  
>>>>>> Jumpstart
>>>>>> your
>>>>>> developing skills, take BlackBerry mobile applications to market
>>>>>> and
>>>>>> stay
>>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>>> now!
>>>>>> http://p.sf.net/sfu/devconference
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Come build with us! The BlackBerry(R) Developer Conference in  
>>>>> SF, CA
>>>>> is the only developer event you need to attend this year.  
>>>>> Jumpstart
>>>>> your
>>>>> developing skills, take BlackBerry mobile applications to market  
>>>>> and
>>>>> stay
>>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register
>>>>> now!
>>>>> http://p.sf.net/sfu/devconference
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Come build with us! The BlackBerry(R) Developer Conference in SF,  
>>>> CA
>>>> is the only developer event you need to attend this year. Jumpstart
>>>> your
>>>> developing skills, take BlackBerry mobile applications to market
>>>> and stay
>>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>>> now!
>>>> http://p.sf.net/sfu/devconference
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart
>>> your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register  
>>> now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart  
>> your
>> developing skills, take BlackBerry mobile applications to market  
>> and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>
> -- 
> View this message in context: http://old.nabble.com/building-on-osx-10.6-tp26063774p28612138.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

To frustrate cross-platform development.

MKG from cell phone

On May 19, 2010 4:32 PM, "Victor Lazzarini" <Victor.Lazzarini@nuim.ie> wrote:

The absence of a C API for GUIs on OSX 10.6 is a major PITA. Why do
they do this?

Victor

On 19 May 2010, at 21:21, Alexis Baskind wrote:

>
> Hi Julian and all,
>
> This thread is a little ...

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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.source...

Hi all,

(Sorry for the previous double posting, I don't know what happened)

Okay, I made some improvements: I was able to build csound in x86_64 on 
10.6. That's the good news. The bad news is that it's without the GUI, 
since part of the csound code directly involves Carbon.

So this is how I did:
     . all the required libraries where built in x86_64
     . download fltk-1.3.x-r7606, which is meant to work with Cocoa
     . build it as a 32/64 bit universal library
         # ./configure CC="gcc -arch x86_64" CXX="g++ -arch x86_64"
         # make
         # make install
     . one line has to be modified in a resulting header file: you have 
to comment the include "include config.h" in /usr/local/include/FL/mac.H
     . going back to csound, the main Sconstruct has to be modified, 
line 609:
         OSXSystemPythonVersions = { 0:0, 1:0, 2:2, 3:3, 4:3, 5:5, 6:6 }
     . also, you have to tell the linker to include Cocoa and 
AudioToolbox frameworks, otherwise it complains. For this, modify the 
three SConstruct files located in the root folder, in the "InOut" folder 
and in "frontends" folder (for the latter I'm not sure it's important, 
since we'll finally build it without frontends): in the three files, 
replace "-framework Carbon" with "-framework Carbon -framework Cocoa 
-framework AudioToolbox"
     . there was also a small mistake in SConstruct, that I guess should 
be corrected in any case:
     line 1345: "lusModule_ = env.Program('%s.so' % targetName, srcs)"
     ... has to be replaced by (I guess):

     "luaModule_ = env.Program('%s.so' % targetName, srcs)"

     . at this stage I was able to do a first build, without the GUI:

     scons dynamicCsoundLibrary=1 buildUtilities=1 buildRelease=1 
noDebug=1 usePortAudio=1 usePortMIDI=1 useFLTK=1buildCsoundVST=0 
buildCsoundAC=1 buildCsound5GUI=0 buildLoris=1 useOSC=1 useUDP=1 
buildPythonOpcodes=1 buildStkOpcodes=1 useCoreAudio=1 buildTclcsound=1 
buildWinsound=1 buildVirtual=1 buildInterfaces=1 buildJavaWrapper=0 
buildOSXGUI=0 buildCSEditor=1 buildNewParser=0 useGettext=1 
buildImageOpcodes=1 useJack=1 Word64=1

     . at the very end you get an error about TclTk directory not 
existing in the resulting framework. Create it:
     # mkdir CsoundLib.framework/Resources/TclTk

     ... and then start building again. It should finish and be happy.

     . the installation with package macker did not work, so I used the 
modified python script provided by Anthony Kozar:
     http://www.anthonykozar.net/csound-macosx/buildingforleopard.html

     So it works, but without GUI, since csound code calls Carbon 
routines in "Fl_Native_File_Chooser_MAC.H" and 
"Fl_Native_File_Chooser_MAC.CXX". It seems that it's the only part in 
the code that should need to be modified to make it run on Cocoa, hopefully.

     Of course the problem is that the resulting binary can not be used 
with i386 code (for instance it fails with csound~  Max/MSP external, or 
with QuteCsound). I believe it should be possible to build it as a 
Mach-O i386/x86_64 binary, so that it can be used in 32bits and in 64 
bits. The problem is that compiling it on 10.6 as a i386 binary implies 
having all libraries that support 32/64 bits, including the standard 
ones (gettext for instance).


     Alexis Baskind



Le 19/05/10 22:47, Michael Gogins a écrit :
 > To frustrate cross-platform development.
 >
 > MKG from cell phone
 >
 >> On May 19, 2010 4:32 PM, "Victor Lazzarini" > > wrote:
 >>
 >> The absence of a C API for GUIs on OSX 10.6 is a major PITA. Why do
 >> they do this?
 >>
 >> Victor
 >>
 >> On 19 May 2010, at 21:21, Alexis Baskind wrote:
 >>
 >> >
 >> > Hi Julian and all,
 >> >
 >> > This thread is a little ...
 >>
 >> 
------------------------------------------------------------------------------
 >>
 >>
 >> _______________________________________________
 >> Csound-devel mailing list
 >> Csound-devel@lists.source...
 >>
 >
 >
 > 
------------------------------------------------------------------------------
 >
 >
 >
 >
 > _______________________________________________
 > Csound-devel mailing list
 > Csound-devel@lists.sourceforge.net
 > https://lists.sourceforge.net/lists/listinfo/csound-devel


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

What part? All GUI code is FLTK, as far as I can tell.

Victor
On 20 May 2010, at 15:27, Alexis Baskind wrote:

> Okay, I made some improvements: I was able to build csound in x86_64  
> on
> 10.6. That's the good news. The bad news is that it's without the GUI,
> since part of the csound code directly involves Carbon.


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yes, for sure. Correct me if I'm wrong (I don't know csound code 
enough), but the only files that make direct calls to Carbon are 
"Fl_Native_File_Chooser_MAC.H" and "Fl_Native_File_Chooser_MAC.CXX", the 
other ones use FLTK calls, right ? So since it seems that FLTK 1.3 may 
be build using Cocoa, modifying those two files should make the GUI work 
on Cocoa. Am I wrong ?

Alexis

Le 20/05/10 16:31, Victor Lazzarini a écrit :
> What part? All GUI code is FLTK, as far as I can tell.
>
> Victor
> On 20 May 2010, at 15:27, Alexis Baskind wrote:
>
>> Okay, I made some improvements: I was able to build csound in x86_64
>> on
>> 10.6. That's the good news. The bad news is that it's without the GUI,
>> since part of the csound code directly involves Carbon.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

I think he means Csound5GUI, which uses Fl_Native_File_Chooser, some
code I found somewhere, and I put in there....
This means Csound5GUI is starting to die its slow death... unless
someone wants to go in and fix this...

Alexis, I really appreciate this effort, since I am running 10.6 on
one of my machines. I would very much like to try your compiled
version if you're willing to package it. If you do so, I can start
providing 64-bit packages of QuteCsound for 10.6.

Cheers,
Andrés

On Thu, May 20, 2010 at 3:31 PM, Victor Lazzarini
 wrote:
> What part? All GUI code is FLTK, as far as I can tell.
>
> Victor
> On 20 May 2010, at 15:27, Alexis Baskind wrote:
>
>> Okay, I made some improvements: I was able to build csound in x86_64
>> on
>> 10.6. That's the good news. The bad news is that it's without the GUI,
>> since part of the csound code directly involves Carbon.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

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

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

yes, you are right. These are not strictly Csound, but part of the  
Csound5GUI frontend, which is effectively deprecated and not  
distributed anymore.

Victor
On 20 May 2010, at 15:48, Alexis Baskind wrote:

> Yes, for sure. Correct me if I'm wrong (I don't know csound code
> enough), but the only files that make direct calls to Carbon are
> "Fl_Native_File_Chooser_MAC.H" and "Fl_Native_File_Chooser_MAC.CXX",  
> the
> other ones use FLTK calls, right ? So since it seems that FLTK 1.3 may
> be build using Cocoa, modifying those two files should make the GUI  
> work
> on Cocoa. Am I wrong ?
>
> Alexis
>
> Le 20/05/10 16:31, Victor Lazzarini a écrit :
>> What part? All GUI code is FLTK, as far as I can tell.
>>
>> Victor
>> On 20 May 2010, at 15:27, Alexis Baskind wrote:
>>
>>> Okay, I made some improvements: I was able to build csound in x86_64
>>> on
>>> 10.6. That's the good news. The bad news is that it's without the  
>>> GUI,
>>> since part of the csound code directly involves Carbon.
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

By the way, did you build from CVS? I am wondering whether the  
modules.c code is using dlopen or not. I had changed it back because  
of portmidi, but not sure I committed it. The dlopen code was required  
for 10.6, but cause trouble with portmidi.

Victor


On 20 May 2010, at 15:48, Alexis Baskind wrote:

> Yes, for sure. Correct me if I'm wrong (I don't know csound code
> enough), but the only files that make direct calls to Carbon are
> "Fl_Native_File_Chooser_MAC.H" and "Fl_Native_File_Chooser_MAC.CXX",  
> the
> other ones use FLTK calls, right ? So since it seems that FLTK 1.3 may
> be build using Cocoa, modifying those two files should make the GUI  
> work
> on Cocoa. Am I wrong ?
>
> Alexis
>
> Le 20/05/10 16:31, Victor Lazzarini a écrit :
>> What part? All GUI code is FLTK, as far as I can tell.
>>
>> Victor
>> On 20 May 2010, at 15:27, Alexis Baskind wrote:
>>
>>> Okay, I made some improvements: I was able to build csound in x86_64
>>> on
>>> 10.6. That's the good news. The bad news is that it's without the  
>>> GUI,
>>> since part of the csound code directly involves Carbon.
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yes I used cvs (last checkout yesterday). I looked at csmodule.c and it 
seems to use dlopen, in function csoundOpenLibrary.

Andres, I'm working on packaging and keep you informed. I don't have 
time to do further testing for the moment (I had to reinstall csound 
5.12.4), so if you can have a look at it and see what works and what 
doesn't it would be great. In my tests it worked as long as no GUI is 
involved in the csd. For instance, xanadu.csd produced the output sound 
file right, but the ftable was not shown.

Alexis

Le 20/05/10 17:03, Victor Lazzarini a écrit :
> By the way, did you build from CVS? I am wondering whether the
> modules.c code is using dlopen or not. I had changed it back because
> of portmidi, but not sure I committed it. The dlopen code was required
> for 10.6, but cause trouble with portmidi.
>
> Victor


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Well then FLTK is not quite right, because the graphics are FLTK-based.

Victor
On 20 May 2010, at 16:19, Alexis Baskind wrote:

> In my tests it worked as long as no GUI is
> involved in the csd. For instance, xanadu.csd produced the output  
> sound
> file right, but the ftable was not shown.
>
> Alexis


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

That's what I was afraid of.

There may be two reasons for that: either the current version of fltk1.3 
(which is still not stable yet), is really not working, or maybe the API 
has changed a little bit, so that it's not compatible anymore with fltk 
1.1.x. Since I don't know fltk I can't tell.

Alexis

Le 20/05/10 17:29, Victor Lazzarini a écrit :
> Well then FLTK is not quite right, because the graphics are FLTK-based.
>
> Victor
> On 20 May 2010, at 16:19, Alexis Baskind wrote:
>
>> In my tests it worked as long as no GUI is
>> involved in the csd. For instance, xanadu.csd produced the output
>> sound
>> file right, but the ftable was not shown.
>>
>> Alexis
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi all,

Before continuing my tests with building an x86_64 version of csound, I 
decided first to build it clean in i386 on osx 10.6. It builds (as longs 
as all the required libraries where built as universal), but when I try 
to run it, I'm facing another problem, with portaudio:

"PortAudio: selected output device 'Built-in Output'
  *** PortAudio: error: Inconsistent full-duplex buffer sizes
Failed to initialise real time audio output
inactive allocs returned to freespace"

It does not seem to depend on the audio interface. By googling I found 
only one post that refers to this error. Victor's advice was then to 
download the latest dev tarball of portaudio, which I did, and it did 
not help, nor with the latest cvs. I tried several things after that:
. build a non-universal i386 version of portaudio
. build portaudio using 10.4u SDK
. use the static portaudio library instead of dynamic, since it seems 
that this is a common advice
. build csound without portaudio, only using coreaudio, but it seems 
that the portaudio is included anyway in the compilations

... but none of those options did help. Any suggestions ?

Alexis


Le 20/05/10 16:49, Andres Cabrera a écrit :
> Hi,
>
> I think he means Csound5GUI, which uses Fl_Native_File_Chooser, some
> code I found somewhere, and I put in there....
> This means Csound5GUI is starting to die its slow death... unless
> someone wants to go in and fix this...
>
> Alexis, I really appreciate this effort, since I am running 10.6 on
> one of my machines. I would very much like to try your compiled
> version if you're willing to package it. If you do so, I can start
> providing 64-bit packages of QuteCsound for 10.6.
>
> Cheers,
> Andrés
>
> On Thu, May 20, 2010 at 3:31 PM, Victor Lazzarini
>   wrote:
>> What part? All GUI code is FLTK, as far as I can tell.
>>
>> Victor
>> On 20 May 2010, at 15:27, Alexis Baskind wrote:
>>
>>> Okay, I made some improvements: I was able to build csound in x86_64
>>> on
>>> 10.6. That's the good news. The bad news is that it's without the GUI,
>>> since part of the csound code directly involves Carbon.
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://li

I think this is a new problem with portaudio because the code I have  
does not cause these problems.
Maybe we need to ask the portaudio list? I'll investigate.

Victor
On 21 May 2010, at 14:37, Alexis Baskind wrote:

> Hi all,
>
> Before continuing my tests with building an x86_64 version of  
> csound, I
> decided first to build it clean in i386 on osx 10.6. It builds (as  
> longs
> as all the required libraries where built as universal), but when I  
> try
> to run it, I'm facing another problem, with portaudio:
>
> "PortAudio: selected output device 'Built-in Output'
>  *** PortAudio: error: Inconsistent full-duplex buffer sizes
> Failed to initialise real time audio output
> inactive allocs returned to freespace"
>
> It does not seem to depend on the audio interface. By googling I found
> only one post that refers to this error. Victor's advice was then to
> download the latest dev tarball of portaudio, which I did, and it did
> not help, nor with the latest cvs. I tried several things after that:
> . build a non-universal i386 version of portaudio
> . build portaudio using 10.4u SDK
> . use the static portaudio library instead of dynamic, since it seems
> that this is a common advice
> . build csound without portaudio, only using coreaudio, but it seems
> that the portaudio is included anyway in the compilations
>
> ... but none of those options did help. Any suggestions ?
>
> Alexis
>
>
> Le 20/05/10 16:49, Andres Cabrera a écrit :
>> Hi,
>>
>> I think he means Csound5GUI, which uses Fl_Native_File_Chooser, some
>> code I found somewhere, and I put in there....
>> This means Csound5GUI is starting to die its slow death... unless
>> someone wants to go in and fix this...
>>
>> Alexis, I really appreciate this effort, since I am running 10.6 on
>> one of my machines. I would very much like to try your compiled
>> version if you're willing to package it. If you do so, I can start
>> providing 64-bit packages of QuteCsound for 10.6.
>>
>> Cheers,
>> Andrés
>>
>> On Thu, May 20, 2010 at 3:31 PM, Victor Lazzarini
>>   wrote:
>>> What part? All GUI code is FLTK, as far as I can tell.
>>>
>>> Victor
>>> On 20 May 2010, at 15:27, Alexis Baskind wrote:
>>>
>>>> Okay, I made some improvements: I was able to build csound in  
>>>> x86_64
>>>> on
>>>> 10.6. That's the good news. The bad news is that it's without the  
>>>> GUI,
>>>> since part of the csound code directly involves Carbon.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Could you send me your actual version of portaudio sources, so that I 
can test if there is a problem related to portaudio, or if I'm doing 
something wrong when building ?

Alexis

Le 21/05/10 15:43, Victor Lazzarini a écrit :
> I think this is a new problem with portaudio because the code I have
> does not cause these problems.
> Maybe we need to ask the portaudio list? I'll investigate.
>
> Victor
> On 21 May 2010, at 14:37, Alexis Baskind wrote:
>
>> Hi all,
>>
>> Before continuing my tests with building an x86_64 version of
>> csound, I
>> decided first to build it clean in i386 on osx 10.6. It builds (as
>> longs
>> as all the required libraries where built as universal), but when I
>> try
>> to run it, I'm facing another problem, with portaudio:
>>
>> "PortAudio: selected output device 'Built-in Output'
>>   *** PortAudio: error: Inconsistent full-duplex buffer sizes
>> Failed to initialise real time audio output
>> inactive allocs returned to freespace"
>>
>> It does not seem to depend on the audio interface. By googling I found
>> only one post that refers to this error. Victor's advice was then to
>> download the latest dev tarball of portaudio, which I did, and it did
>> not help, nor with the latest cvs. I tried several things after that:
>> . build a non-universal i386 version of portaudio
>> . build portaudio using 10.4u SDK
>> . use the static portaudio library instead of dynamic, since it seems
>> that this is a common advice
>> . build csound without portaudio, only using coreaudio, but it seems
>> that the portaudio is included anyway in the compilations
>>
>> ... but none of those options did help. Any suggestions ?
>>
>> Alexis
>>
>>
>> Le 20/05/10 16:49, Andres Cabrera a écrit :
>>> Hi,
>>>
>>> I think he means Csound5GUI, which uses Fl_Native_File_Chooser, some
>>> code I found somewhere, and I put in there....
>>> This means Csound5GUI is starting to die its slow death... unless
>>> someone wants to go in and fix this...
>>>
>>> Alexis, I really appreciate this effort, since I am running 10.6 on
>>> one of my machines. I would very much like to try your compiled
>>> version if you're willing to package it. If you do so, I can start
>>> providing 64-bit packages of QuteCsound for 10.6.
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Thu, May 20, 2010 at 3:31 PM, Victor Lazzarini
>>>    wrote:
>>>> What part? All GUI code is FLTK, as far as I can tell.
>>>>
>>>> Victor
>>>> On 20 May 2010, at 15:27, Alexis Baskind wrote:
>>>>
>>>>> Okay, I made some improvements: I was able to build csound in
>>>>> x86_64
>>>>> on
>>>>> 10.6. That's the good news. The bad news is that it's without the
>>>>> GUI,
>>>>> since part of the csound code directly involves Carbon.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>


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

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net