The Csound license permits anyone to use, modify, or redistribute Csound as 
long as any software that is based on Csound or uses Csound has the same 
license.

You can include the library and/or sources with your installer, or include 
the Csound installer in or with your installer.

For me personally, this is all fine as well. Of course I am always concerned 
that the Csound developer community, which is not large, keep working within 
a single body of code instead of branching off into separate versions with 
potential incompatibilities and unnecessary duplications of effort.

But it doesn't sound like you're doing that at all. It sounds like you're 
planning to use the Csound library as is, for the "csound engine" in your 
application, right? That's just the kind of thing I'm trying to make 
possible. If you need changes to Csound I hope that we can provide them 
within the Csound library.

Regards,
Mike

----- Original Message ----- 
From: "matt ingalls" 
To: "Developer discussions" 
Sent: Monday, May 29, 2006 4:40 PM
Subject: [Cs-dev] license question


> as i understand the csound license, i can distribute csound freely
>
> so, for instance, i can include it within an installer for my app
> so i don't have to make users make an extra trip to sourceforge
> to get csoundLib.  - right?
>
> what about embedding the csoundLib installer inside my MacOS application
> bundle?  so i could have my application check for csoundLib on launch,
> and if not there run the CsoundLib installer??
>
> thanks,
> matt
>
>
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 




_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

yes - i am just wondering about distribution...

thanks,
m


On May 29, 2006, at 3:48 PM, Michael Gogins wrote:

> The Csound license permits anyone to use, modify, or redistribute  
> Csound as
> long as any software that is based on Csound or uses Csound has the  
> same
> license.
>
> You can include the library and/or sources with your installer, or  
> include
> the Csound installer in or with your installer.
>
> For me personally, this is all fine as well. Of course I am always  
> concerned
> that the Csound developer community, which is not large, keep  
> working within
> a single body of code instead of branching off into separate  
> versions with
> potential incompatibilities and unnecessary duplications of effort.
>
> But it doesn't sound like you're doing that at all. It sounds like  
> you're
> planning to use the Csound library as is, for the "csound engine"  
> in your
> application, right? That's just the kind of thing I'm trying to make
> possible. If you need changes to Csound I hope that we can provide  
> them
> within the Csound library.
>
> Regards,
> Mike
>
> ----- Original Message -----
> From: "matt ingalls" 
> To: "Developer discussions" 
> Sent: Monday, May 29, 2006 4:40 PM
> Subject: [Cs-dev] license question
>
>
>> as i understand the csound license, i can distribute csound freely
>>
>> so, for instance, i can include it within an installer for my app
>> so i don't have to make users make an extra trip to sourceforge
>> to get csoundLib.  - right?
>>
>> what about embedding the csoundLib installer inside my MacOS  
>> application
>> bundle?  so i could have my application check for csoundLib on  
>> launch,
>> and if not there run the CsoundLib installer??
>>
>> thanks,
>> matt
>>
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net