Just now I have built the core of Csound plus most utilities and many
plugin opcodes with Microsoft Visual Studio Community 2015. Thanks to
Stephen Kyne, Steven Yi, and others for moving this forward.

For the next release of Csound, I would like to build the Windows
installer using Visual Studio. This would among other things make it
easier to set up the build, easier to debug Csound, and easier to
integrate Csound with NW.js, node.js, CsoundQt, and other such
systems. In the near future it should be possible for a new release
tag to simply show up in the releases as a finished, tested installer.

However, over the years I have made it a point to cram as many
features, front ends, and whatnot into the Windows installer as
possible. Now may be a good time to consider what really needs to be
in there. (Please note, not being in the Windows installer does NOT
mean not being in the Csound Git repository!)

I will continue to provide CsoundVST and the vst4cs opcodes on my own
Web site. I also plan to keep the csound.node addon for NW.js and the
Ableton Live opcodes.

But what about --

(1) The FluidSynth opcodes? Do you ever use them, or not?
(2) The Java interfaces? Do you ever use them, or not?
(3) The LuaJIT opcodes? Do you ever use them, or not?
(4) The CsoundAC algorithmic composition system? Do you ever use it,
or not? If nobody but me ever uses it, I may move it to my own
repository.
(5) The STK (C++) opcodes? Do you ever use them, or not?
(6) The CsoundQt "front end" for running Csound? Do you ever use it,
or not? If so, do you get it from the CsoundQt repo or from the Csound
repo?
(7) The linear algebra opcodes? Do you ever use them, or not?
(8) The FLTK widgets? Do you ever use them, or not?

Please comment on the above or any other issues for the Windows installer.

Thanks,
Mike





-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com

>From me:

(1) The FluidSynth opcodes? Do you ever use them, or not?
I have used them (but not for my own music) and I think many people do use them

(2) The Java interfaces? Do you ever use them, or not?
Blue depends on them, so lots of users do. I have used them for some demos.

(3) The LuaJIT opcodes? Do you ever use them, or not?
I have tested them in the past, not sure what their status is.

(4) The CsoundAC algorithmic composition system? Do you ever use it,
or not? If nobody but me ever uses it, I may move it to my own
repository.
I think this is a good idea, and would provide some more width for 
developing them as a Csound-based project.

(5) The STK (C++) opcodes? Do you ever use them, or not?
No, but I think a number of peopple do.

(6) The CsoundQt "front end" for running Csound? Do you ever use it,
or not? If so, do you get it from the CsoundQt repo or from the Csound
repo?
I use it regularly, usually the latest version so I can test it before
packaging.

(7) The linear algebra opcodes? Do you ever use them, or not?
No, but, again, I think some people do.

(8) The FLTK widgets? Do you ever use them, or not?
I replaced them by CsoundQT since it came out, but use them if looking at older
code that employs them.


========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 12 Jun 2017, at 01:44, Michael Gogins  wrote:
> 
> Just now I have built the core of Csound plus most utilities and many
> plugin opcodes with Microsoft Visual Studio Community 2015. Thanks to
> Stephen Kyne, Steven Yi, and others for moving this forward.
> 
> For the next release of Csound, I would like to build the Windows
> installer using Visual Studio. This would among other things make it
> easier to set up the build, easier to debug Csound, and easier to
> integrate Csound with NW.js, node.js, CsoundQt, and other such
> systems. In the near future it should be possible for a new release
> tag to simply show up in the releases as a finished, tested installer.
> 
> However, over the years I have made it a point to cram as many
> features, front ends, and whatnot into the Windows installer as
> possible. Now may be a good time to consider what really needs to be
> in there. (Please note, not being in the Windows installer does NOT
> mean not being in the Csound Git repository!)
> 
> I will continue to provide CsoundVST and the vst4cs opcodes on my own
> Web site. I also plan to keep the csound.node addon for NW.js and the
> Ableton Live opcodes.
> 
> But what about --
> 
> (1) The FluidSynth opcodes? Do you ever use them, or not?
> (2) The Java interfaces? Do you ever use them, or not?
> (3) The LuaJIT opcodes? Do you ever use them, or not?
> (4) The CsoundAC algorithmic composition system? Do you ever use it,
> or not? If nobody but me ever uses it, I may move it to my own
> repository.
> (5) The STK (C++) opcodes? Do you ever use them, or not?
> (6) The CsoundQt "front end" for running Csound? Do you ever use it,
> or not? If so, do you get it from the CsoundQt repo or from the Csound
> repo?
> (7) The linear algebra opcodes? Do you ever use them, or not?
> (8) The FLTK widgets? Do you ever use them, or not?
> 
> Please comment on the above or any other issues for the Windows installer.
> 
> Thanks,
> Mike
> 
> 
> 
> 
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com

> (1) The FluidSynth opcodes? Do you ever use them, or not?
Yes

> (2) The Java interfaces? Do you ever use them, or not?
No

> (3) The LuaJIT opcodes? Do you ever use them, or not?
No

> (4) The CsoundAC algorithmic composition system? Do you ever use it,
> or not? 
No

> (5) The STK (C++) opcodes? Do you ever use them, or not?
No. Whenever I have needed something similar to the STK models I used the 
faust port compiled to csound. 

> (6) The CsoundQt "front end" for running Csound? Do you ever use it,
> or not? If so, do you get it from the CsoundQt repo or from the Csound
> repo?

Yes, very much so. For me I tend to compile the latest version, but I do 
rely heavily on the fact that other users have it installed by default

> (7) The linear algebra opcodes? Do you ever use them, or not?
No

> (8) The FLTK widgets? Do you ever use them, or not?
There is a welth of demos/orchestras which use them, so they are nice to 
have. 

Eduardo Moguillansky

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Is this addresses just to Windows users or more general?

On Sun, 11 Jun 2017, Michael Gogins wrote:

> Just now I have built the core of Csound plus most utilities and many
> plugin opcodes with Microsoft Visual Studio Community 2015. Thanks to
> Stephen Kyne, Steven Yi, and others for moving this forward.
>
> For the next release of Csound, I would like to build the Windows
> installer using Visual Studio. This would among other things make it
> easier to set up the build, easier to debug Csound, and easier to
> integrate Csound with NW.js, node.js, CsoundQt, and other such
> systems. In the near future it should be possible for a new release
> tag to simply show up in the releases as a finished, tested installer.
>
> However, over the years I have made it a point to cram as many
> features, front ends, and whatnot into the Windows installer as
> possible. Now may be a good time to consider what really needs to be
> in there. (Please note, not being in the Windows installer does NOT
> mean not being in the Csound Git repository!)
>
> I will continue to provide CsoundVST and the vst4cs opcodes on my own
> Web site. I also plan to keep the csound.node addon for NW.js and the
> Ableton Live opcodes.
>
> But what about --
>
> (1) The FluidSynth opcodes? Do you ever use them, or not?
> (2) The Java interfaces? Do you ever use them, or not?
> (3) The LuaJIT opcodes? Do you ever use them, or not?
> (4) The CsoundAC algorithmic composition system? Do you ever use it,
> or not? If nobody but me ever uses it, I may move it to my own
> repository.
> (5) The STK (C++) opcodes? Do you ever use them, or not?
> (6) The CsoundQt "front end" for running Csound? Do you ever use it,
> or not? If so, do you get it from the CsoundQt repo or from the Csound
> repo?
> (7) The linear algebra opcodes? Do you ever use them, or not?
> (8) The FLTK widgets? Do you ever use them, or not?
>
> Please comment on the above or any other issues for the Windows installer.
>
> Thanks,
> Mike
>
>
>
>
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

> (1) The FluidSynth opcodes? Do you ever use them, or not?

I am not currently using these.

> (2) The Java interfaces? Do you ever use them, or not?

Yes. Blue depends upon the Java interface. I have also done some
experiments with using the Java interface through other JVM languages
(particularly Clojure).

> (3) The LuaJIT opcodes? Do you ever use them, or not?

No.

> (4) The CsoundAC algorithmic composition system? Do you ever use it,
> or not? If nobody but me ever uses it, I may move it to my own
> repository.

I do not use these and I'd prefer to see these moved to a separate
repository. It slows down builds here, and if something doesn't
compile within CsoundAC, I usually do not have the time/knowledge to
investigate and end up turning off building CsoundAC altogether.

> (5) The STK (C++) opcodes? Do you ever use them, or not?

No.

> (6) The CsoundQt "front end" for running Csound? Do you ever use it,
> or not? If so, do you get it from the CsoundQt repo or from the Csound
> repo?

I do not use CsoundQT usually, but I like to have access to it to
investigate things people have done using it. I think it would be good
to have in the installer.

> (7) The linear algebra opcodes? Do you ever use them, or not?

No.

> (8) The FLTK widgets? Do you ever use them, or not?

Not personally, but I do like access to it to test other's project
which use it. (Not sure if it's relevlant, but I do use the FLTK
Virtual Keyboard on occasion.)

Thanks!
steven

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Michael,

For my part:

(1) The FluidSynth opcodes? YES
(2) The Java interfaces? YES
(3) The LuaJIT opcodes? NO
(4) The CsoundAC algorithmic composition system? YES 
(5) The STK (C++) opcodes? YES
(6) The CsoundQt "front end" for running Csound? YES
(7) The linear algebra opcodes? YES 
(8) The FLTK widgets? YES

The link to your built of Csound 6.09.1 is broken.

 Thanks,
Marc


Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

i never used windows myself, but i would like to second eduardo's 
assessment about csoundqt intergration.  for students and in particular 
new csound users it is good to see csoundqt immediately after the 
installation in the Programs menu.

as we discussed on the csoundqt mailing list, i would like to see a 
version of csoundqt here as default which comes with rtmidi but without 
python as default, so that people can really run it out of the box, 
without having python on board.

	joachim



On 12/06/17 12:29, Eduardo Moguillansky wrote:
>> (6) The CsoundQt "front end" for running Csound? Do you ever use it,
>> or not? If so, do you get it from the CsoundQt repo or from the Csound
>> repo?
>
> Yes, very much so. For me I tend to compile the latest version, but I do
> rely heavily on the fact that other users have it installed by default

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here