Change to user includes then, and I'll see what happens here. The include
paths are not
controlled only by the system anyway, but also by the SConstruct file.


----- Original Message ----- 
From: "Anthony Kozar" 
To: "Csound Developers Discussion List" 
Sent: Thursday, June 24, 2004 9:31 PM
Subject: [CSOUND-DEV:4843] Re: progress on MacOS 9


> On 6/24/04 9:11 PM, Michael Gogins etched in stone:
>
> > Both of the duplicate copies of sdf.c etc. are needed because SCons
needs 2
> > ..o files, and its rules are such that for 2 .o files, it needs two
source
> > files.
>
> As long as the two copies always stay in sync, this shouldn't be a problem
> (although I am confused as to why you need two object files).
>
> > Please leave the #includes as is.
>
> This is a problem.  The compiler looks for system headers in different
> locations than user code and these files aren't located in the system
> locations.  Why can't we use "" instead of <> ?
>
> >> #include 
> >> #include 
> >>
> >> Shouldn't they be non-system includes?:
> >>
> >> #include "H/sdif-mem.h"   // or just "sdif-mem.h"
> >> #include "H/sdif.h"       // and "sdif.h"
>
> Thanks.
>
> Anthony Kozar
> anthony.kozar@utoledo.edu
> http://akozar.spymac.net/
>