----- Original Message -----

From: Rory Walsh

To: CSOUND-DEV@LISTSERV.HEANET.IE

Sent: Sunday, October 25, 2015 10:06 AM

Subject: Re: [Csnd-dev] Cabbage for Windows installer

If each plugin opcode uses ' -static-libstdc++ -static' or '-static-libgcc -static' then it might work, but in the past I've had quite a few problems getting my binaries to work with yours. Apart from that, I don't see why we should ship an extra front-end for Csound on Windows, when we don't offer the same package on OSX? Is this not further confusion for new users who move from one OS to another and expect the same toolset? 

I've always thought that Csound packages should only ever contain core Csound libraries and the standard CLI, and that front-end developers should themselves be responsible for the development, maintenance and distribution of their applications. I think I'm alone in feeling this way however :(

Rory.

>
> Can your version be installed to use an existing installation of Csound?
>
> Regards,
> Mike
>
> On Oct 25, 2015 7:14 AM, "Rory Walsh" <rorywalsh@ear.ie> wrote:
>>
>> If you must include one then Cabbage is the one to use. however, I would prefer if Cabbage was not included with the standard Windows installer. I would rather users download and use the most current version available from the Cabbage website.
>>
>> On 25 October 2015 at 03:45, Michael Gogins <michael.gogins@gmail.com> wrote:
>>>
>>> Which version should I use, cabbage or cabbage studio, to bundle with Csound in the windows installer?
>>>
>>> Regards,
>>> Mike
>>
>>

I have removed Cabbage from the Windows installer due partly to the
author's request but also because of the library linkage compatibility
problems that have been reported.

The Windows installer will still include CsoundQt built by me with the
HTML5 features enabled, and csound-node for NW.js on Windows.

Regards,
Mike

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


On Sun, Oct 25, 2015 at 2:22 PM, Art Hunkins  wrote:
> I agree with Rory on this.
>
> One "standard" frontend per distribution is surely enough - if not too much.
>
> The developer of a frontend indeed need be completely responsible for
> maintaining and developing their own particular software.
>
> Art Hunkins
>
> ----- Original Message -----
> From: Rory Walsh
> To: CSOUND-DEV@LISTSERV.HEANET.IE
> Sent: Sunday, October 25, 2015 10:06 AM
> Subject: Re: [Csnd-dev] Cabbage for Windows installer
>
> If each plugin opcode uses ' -static-libstdc++ -static' or '-static-libgcc
> -static' then it might work, but in the past I've had quite a few problems
> getting my binaries to work with yours. Apart from that, I don't see why we
> should ship an extra front-end for Csound on Windows, when we don't offer
> the same package on OSX? Is this not further confusion for new users who
> move from one OS to another and expect the same toolset?
>
> I've always thought that Csound packages should only ever contain core
> Csound libraries and the standard CLI, and that front-end developers should
> themselves be responsible for the development, maintenance and distribution
> of their applications. I think I'm alone in feeling this way however :(
>
> Rory.
>
>
>>
>> Can your version be installed to use an existing installation of Csound?
>>
>> Regards,
>> Mike
>>
>> On Oct 25, 2015 7:14 AM, "Rory Walsh"  wrote:
>>>
>>> If you must include one then Cabbage is the one to use. however, I would
>>> prefer if Cabbage was not included with the standard Windows installer. I
>>> would rather users download and use the most current version available from
>>> the Cabbage website.
>>>
>>> On 25 October 2015 at 03:45, Michael Gogins 
>>> wrote:
>>>>
>>>> Which version should I use, cabbage or cabbage studio, to bundle with
>>>> Csound in the windows installer?
>>>>
>>>> Regards,
>>>> Mike
>>>