Hi,

I just was confirmed that the beosc opcodes (beosc, beadsynt, etc., 
defined in Opcodes/emugens/beosc.c) are not included in the windows 
installer and the windows builds done by appveyor. Is there a reason for 
this? These were released with 6.12.

There is not cmake option to not build these alone, either all emugens 
are built or none, so being that other opcodes there are present (bpf, 
printarray, etc.) it seems that only this file is not being built.

---

Looks like it was not in the installer build script. I added a line and pushed the change to github:

https://github.com/csound/csound/commit/642ff48fd3be59d61fabe502f9f645677bc65ad1  

Let's see what happens in the next appveyor build. 

On Wed, Apr 24, 2019 at 9:44 AM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

I just was confirmed that the beosc opcodes (beosc, beadsynt, etc.,
defined in Opcodes/emugens/beosc.c) are not included in the windows
installer and the windows builds done by appveyor. Is there a reason for
this? These were released with 6.12.

There is not cmake option to not build these alone, either all emugens
are built or none, so being that other opcodes there are present (bpf,
printarray, etc.) it seems that only this file is not being built.

---

eduardo