Csound Csound-dev Csound-tekno Search About

[Csnd-dev] quick question regarding OSX install...

Date2015-10-23 15:09
FromRory Walsh
Subject[Csnd-dev] quick question regarding OSX install...
I gave up on including the full Csound binaries with Cabbage due to the bundle size growing to about 600Mbs!  No problem. I'm just going to offer an option to install Csound with Cabbage. My question is this. Will placing CsoundLib64.framework into Library/Frameworks install Csound. Or are there any kind of system links or environment variables also set up when installing from Victor's package? It seems to work fine doing it this way, but I want to know for sure. For example, if someone has a version of Csound installed from Victor's package, and the Cabbage installer overwrites only the framework with a newer of different version, will it causes any problems?

Date2015-10-23 15:16
FromMichael Gogins
SubjectRe: [Csnd-dev] quick question regarding OSX install...
600 megabytes would be far from largest software package that I have
downloaded and installed recently, so maybe you shouldn't worry too
much. Base your evaluation on a survey of other things happening in
the same space.

Regards,
Mike

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


On Fri, Oct 23, 2015 at 10:09 AM, Rory Walsh  wrote:
> I gave up on including the full Csound binaries with Cabbage due to the
> bundle size growing to about 600Mbs!  No problem. I'm just going to offer an
> option to install Csound with Cabbage. My question is this. Will placing
> CsoundLib64.framework into Library/Frameworks install Csound. Or are there
> any kind of system links or environment variables also set up when
> installing from Victor's package? It seems to work fine doing it this way,
> but I want to know for sure. For example, if someone has a version of Csound
> installed from Victor's package, and the Cabbage installer overwrites only
> the framework with a newer of different version, will it causes any

Date2015-10-23 15:41
FromRory Walsh
SubjectRe: [Csnd-dev] quick question regarding OSX install...
It's more the size of each exported plugin that contains Csound. if users are creating 20 different plugins, that will take over a gb of space. On there own each is about 10mbs. So it's not really practical in this sense to bundle Csound with each one. If users want to create completely standalone products that bundle Csound I'm happy to help them with it. Otherwise I think it's easiest to simply include the Csound frameworks and place it in the correct location. 

On 23 October 2015 at 15:16, Michael Gogins <michael.gogins@gmail.com> wrote:
600 megabytes would be far from largest software package that I have
downloaded and installed recently, so maybe you shouldn't worry too
much. Base your evaluation on a survey of other things happening in
the same space.

Regards,
Mike

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


On Fri, Oct 23, 2015 at 10:09 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> I gave up on including the full Csound binaries with Cabbage due to the
> bundle size growing to about 600Mbs!  No problem. I'm just going to offer an
> option to install Csound with Cabbage. My question is this. Will placing
> CsoundLib64.framework into Library/Frameworks install Csound. Or are there
> any kind of system links or environment variables also set up when
> installing from Victor's package? It seems to work fine doing it this way,
> but I want to know for sure. For example, if someone has a version of Csound
> installed from Victor's package, and the Cabbage installer overwrites only
> the framework with a newer of different version, will it causes any
> problems?


Date2015-10-23 15:43
FromMichael Gogins
SubjectRe: [Csnd-dev] quick question regarding OSX install...
OK, I get it now.

Regards,
Mike

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


On Fri, Oct 23, 2015 at 10:41 AM, Rory Walsh  wrote:
> It's more the size of each exported plugin that contains Csound. if users
> are creating 20 different plugins, that will take over a gb of space. On
> there own each is about 10mbs. So it's not really practical in this sense to
> bundle Csound with each one. If users want to create completely standalone
> products that bundle Csound I'm happy to help them with it. Otherwise I
> think it's easiest to simply include the Csound frameworks and place it in
> the correct location.
>
> On 23 October 2015 at 15:16, Michael Gogins 
> wrote:
>>
>> 600 megabytes would be far from largest software package that I have
>> downloaded and installed recently, so maybe you shouldn't worry too
>> much. Base your evaluation on a survey of other things happening in
>> the same space.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Fri, Oct 23, 2015 at 10:09 AM, Rory Walsh  wrote:
>> > I gave up on including the full Csound binaries with Cabbage due to the
>> > bundle size growing to about 600Mbs!  No problem. I'm just going to
>> > offer an
>> > option to install Csound with Cabbage. My question is this. Will placing
>> > CsoundLib64.framework into Library/Frameworks install Csound. Or are
>> > there
>> > any kind of system links or environment variables also set up when
>> > installing from Victor's package? It seems to work fine doing it this
>> > way,
>> > but I want to know for sure. For example, if someone has a version of
>> > Csound
>> > installed from Victor's package, and the Cabbage installer overwrites
>> > only
>> > the framework with a newer of different version, will it causes any
>> > problems?
>