OK, that should work.

I think Steven still has a point with simplifying the headers for clients of the API. I can easily imagine clients that need to #include  and this brings in many other headers, no?

By the way, CsoundVST with latest CVS sources is building and working. I only had to make one minor change (the output soundfile name is now being blanked out after csound finishes running so I have to save it in CsoundVST after compiling). So, thanks for your attention to CsoundVST when changing the ENVIRON to CSOUND.

Regards,
Mike

-----Original Message-----
From: Istvan Varga 
Sent: Aug 17, 2005 11:46 AM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] csound.h

Michael Gogins wrote:

> I might want to include csoundCore.h.
 > At present, I guess this means I would have to ONLY include
 > that and not csound.h, is that correct?

No, csoundCore.h should not be included by anything that is not
part of the engine (that is, files in Engine, OOps, Top, and InOut,
not including any plugins). If you want to have the functionality
of both csound.h and csdl.h, it is currently possible to include
these two headers from the same file (csound.h first, and then
csdl.h); beware, however, that many of the functions that can be
found in the CSOUND structure, but not in csound.h or files included
by csound.h may not always work correctly when called directly by a
host application. Possible problems include uses of ids, pds, curip,
or other variables in CSOUND that are only valid while the various
"perform" functions are being called, and longjmp.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael Gogins wrote:

> By the way, CsoundVST with latest CVS sources is building and
> working. I only had to make one minor change (the output soundfile
> name is now being blanked out after csound finishes running so I have
> to save it in CsoundVST after compiling). So, thanks for your
> attention to CsoundVST when changing the ENVIRON to CSOUND.

I made a number of changes to CsoundVST sources to fix compile
errors, although the main issue was not the renaming of ENVIRON to
CSOUND (this was done with a simple program that was run on all source
files), but the replacement of void* instance pointers with ENVIRON*
(now CSOUND*) and some of the header changes.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven Yi wrote:

> Also, certain macros need to be defined for those headers to work out
> correctly, yes?  If I am building a separate application, what's the
> best way to convey those macros which need to be defined?

You do not need to define macros to select the type of interface (host
or plugin) to be used; rather than that, the interface is selected by
including csound.h or csdl.h. I also changed sysdep.h to make it work
- at least for externals - even without the various system dependent
macros (LINUX, WIN32, HAVE_*, etc.), although defining macros may still
be needed on Mac platforms or compilers other than GCC.
USE_DOUBLE should be defined when compiling for a double precision
Csound library.



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net