It should be noted that this will be a minor difference
between
Macs and other platforms, as the mac headers don't go into
a subdirectory called csound.

A way round is to write the headers  as before and
add -I/usr/local/lib/csound to the compiler.

It would be good if the include directive was the same
across
all platforms. I can I suppose move everything into a
subdirectory called 'csound', under "Headers', but that
seems
to make little sense on the mac.

How's it going to be on Windows?

Victor

>
> Ah, okay, must be just old installation artifacts I never
> cleaned up then.  Thanks!
>
> BTW: I was thinking today that it's a bit strange that for
> frontends that are in CS5 CVS, because the H dir is
> included in the build properties, they reference directly
> the header and not , while end users who may
> build a program on top of CS5 will have to use
> .  So the frontends examples don't quite
> reflect what an end user would experience, and the H dir
> is not set up in a way reflective of the installed
> directory structure.  It's really a minor issue in the end
> , but curious nevertheless, and perhaps would require a
> note to developer users who will be using the C/C++ API.
>
> steven
>
> On 12/21/05, Istvan Varga  wrote:
> > On Wednesday 21 December 2005 08:21, Steven Yi wrote:
> >
> > > BTW: regardless of include base dir (i.e. /usr/include
> > > , /usr/local/include), are the headers going into
> > > "Csound" or "csound" or neither?  I seem to have both
> > > here from running installs so can't remember who's
> > > releases did what, but this affects end users who will
> develop on top of the C API if it is not consistent.  My
> > > preference is for "csound", i.e.
> > > "/usr/local/include/csound" with all relevant headers
> there.  Any thoughts? >
> > I used /usr/local/include/Csound originally, but
> > switched to /usr/local/include/csound as you suggested.
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you
> > grep through log files for problems?  Stop!  Download
> > the new AJAX search engine that makes searching your log
> > files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> >
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files for problems?  Stop!  Download the new
> AJAX search engine that makes searching your log files as
> easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id865&opclick
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net