Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:4325] Re: Csound 5 SConstruct

Date2004-03-15 18:13
From"gogins@pipeline.com"
Subject[CSOUND-DEV:4325] Re: Csound 5 SConstruct
There is no support in my SConstruct for Macs yet... maybe you could
provide that?

Original Message:
-----------------
From: stevenyi stevenyi@csounds.com
Date: Mon, 15 Mar 2004 09:50:47 -0800
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4323] Re: Csound 5 SConstruct


Yes, I see the new changes from John in the CVS require some SConstruct
changes.  Heading off to work now, I'll try out a compile out on WinXP
later today and perhaps will be able to work on the SConstruct there as
well.  I'll also give it a go on the SourceForge compile farm for
MacOSX, though that won't build for realtime as PortAudio v19 is not
implemented yet for MacOSX.  =(  At least this will see if the file can
build without realtime.

Thanks again for the work with this!  It's already made things easier
for me. =)

steven


On Mon, 2004-03-15 at 06:29, gogins@pipeline.com wrote:
> Thanks for your input. I've made some of the fixes you made, and some
> others as well, but I've also found other things breaking, in some cases
> because John Fitch and I are both working on the code and files sometimes
> get out of synch.
> 
> And thanks for booking your changes in!


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

Date2004-03-15 19:53
Fromsteven yi
Subject[CSOUND-DEV:4326] Re: Csound 5 SConstruct
I'm certainly willing to give it a try. =) 

BTW: I've checked in another change for the SConstruct file.  I was 
getting a KeyError exception when trying to set some environment 
variables.  Your comments listed the section as being for Visual Studio 
which I do not have installed here.  I wrapped that area of code with 
some exception handling that ignores that area of setup.  Probably could 
be done more atomically per line, but the quick solution works.

steven

gogins@pipeline.com wrote:

>There is no support in my SConstruct for Macs yet... maybe you could
>provide that?
>
>Original Message:
>-----------------
>From: stevenyi stevenyi@csounds.com
>Date: Mon, 15 Mar 2004 09:50:47 -0800
>To: csound-dev@eartha.mills.edu
>Subject: [CSOUND-DEV:4323] Re: Csound 5 SConstruct
>
>
>Yes, I see the new changes from John in the CVS require some SConstruct
>changes.  Heading off to work now, I'll try out a compile out on WinXP
>later today and perhaps will be able to work on the SConstruct there as
>well.  I'll also give it a go on the SourceForge compile farm for
>MacOSX, though that won't build for realtime as PortAudio v19 is not
>implemented yet for MacOSX.  =(  At least this will see if the file can
>build without realtime.
>
>Thanks again for the work with this!  It's already made things easier
>for me. =)
>
>steven
>
>
>On Mon, 2004-03-15 at 06:29, gogins@pipeline.com wrote:
>  
>
>>Thanks for your input. I've made some of the fixes you made, and some
>>others as well, but I've also found other things breaking, in some cases
>>because John Fitch and I are both working on the code and files sometimes
>>get out of synch.
>>
>>And thanks for booking your changes in!
>>    
>>
>
>
>--------------------------------------------------------------------
>mail2web - Check your email from the web at
>http://mail2web.com/ .
>
>
>
>
>  
>

Date2004-03-15 20:21
Fromsteven yi
Subject[CSOUND-DEV:4327] Re: Csound 5 SConstruct
I the SConstruct file to reflect the removal of files from CVS:

soundio.c
soundin.c
ieee80.c

Compiling now, I get to an error in Opcodes/moog1.c:

Opcodes/moog1.c: In function `Samp_tick':
Opcodes/moog1.c:146: error: structure has no member named `h'
Opcodes/moog1.c:152: error: structure has no member named `h'

I'm pretty sure this has to do with the macro's from csdl.h redefining 
printf, but I can't figure out what the proper fix is.  This code is 
just debug code, so I commented out to get past it. Besides that one 
hitch, I've managed to get through compiling and now am just having some 
errors with linking (I expected these, though, as I think I have some of 
the dependent libraries compiled with mingw or cygwin or vice versa).

steven