As far as I can gather, the copyrights for original Csound allow use as long as you're not redistributing/selling Csound. Where do these rules stand on creating and selling a program that depends on Csound and the API?

Pete

Csound is licensed under the GNU Lesser General Public License,
version 2.1. That contains the answer to your question, implicitly.

Explicitly, you are permitted to use Csound in a closed source
application under the following conditions:

1) If you link with the existing Csound DLL, i.e. do not statically
link with any Csound code, you may go right ahead.

2) If you link with any Csound code statically, then you must make any
changes that you make to Csound source code publicly available under
the LGPL v2.1 "from the same place" as your application.

Short answer: Use only shared libraries/DLLs/dynamic linking with all
Csound code and you are OK. It must be possible to swap any Csound
shared libraries that you distribute with your app out for the same
shared libraries from the Csound distribution. This usually should not
present any difficulty.

Commercial iOS apps have till now required static linking, so they're
out unless it is now OK to use dynamic linking.

Android apps can use dynamic linking, as Csound for Android does (it
is open source, but legally could be closed source).

I am not a lawyer, but this is my best understanding of the situation.

Regards,
Mike




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


On Fri, Aug 7, 2015 at 1:16 PM, Peter Burgess
 wrote:
> As far as I can gather, the copyrights for original Csound allow use as long
> as you're not redistributing/selling Csound. Where do these rules stand on
> creating and selling a program that depends on Csound and the API?
>
> Pete
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> 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

Thanks! I'm just going to be using the API, so it sounds like I should be fine. So what would count as statically linking to the code?
So, if I've understood correctly, that means I'm allowed to have Csound as part of my package ie. I could have csound inside the program's directory to help make it work off the bat without downloading it separately?

It sounds like you are running Csound as a separate program using a .bat file, is that correct?  Or are you compiling your program to incorporate Csound and run it by calling functions in Csound? In that case, dynamic linking uses the Csound DLL.   Static linking uses only the Csound .lib (Microsoft) or .a (MinGW) file.

Regards,
Mike

I am hazy about licencing but I think if you distribute the csound 
binaries you have to o ffer the csound sources as well.  Or at least say 
from whence they can be down-loaded


On Sat, 8 Aug 2015, Peter Burgess wrote:

> 
> Thanks! I'm just going to be using the API, so it sounds like I should be
> fine. So what would count as statically linking to the code?
> So, if I've understood correctly, that means I'm allowed to have Csound as
> part of my package ie. I could have csound inside the program's directory to
> help make it work off the bat without downloading it separately?
> 
> 
>

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