I recommend only compiling opcodes as plugins. Just #include csdl.h and
follow the other instructions in csound.pdf. If you want to not compile this
way, you can #include cs.h, and spell out all the signatures of the ENVIRON
functions. Such opcodes will compile either way. See the fluid opcode for
examples of how to do this.

----- Original Message ----- 
From: "Alex Norman" 
To: "Csound Developers Discussion List" 
Sent: Sunday, May 09, 2004 11:29 PM
Subject: [CSOUND-DEV:4640] csound 5 plugin vs. csound 4 compiled in


> Hello,
> I have some Csound ugens that I'm releasing that work like pvread/add..
except
> use ATS files.  I'm wondering if there is a specific macro statement that
people
> are using so that you can either include cs.h or csdl.h, something like:
> #ifdef CSOUND5_PLUGIN
> #include "csdl.h"
> #else
> #include "cs.h"
> #endif
>
> Also, besides including csdl.h the static OENTRY, opcode_size, and
> opcode_init, is there anything that I have to do to make my opcode work as
a
> Csound 5 plug-in?
>
> Thanks,
> Alex Norman
>
>