[chuck-users] embedding ChucK, and Windows8, ARM, etc.

henrique matias hems.inlet at gmail.com
Tue Feb 12 11:30:40 EST 2013


This licence thing is a very tuff subject, indeed! I wish the world were
easier!!


----- A bit of OT -----

I must say your point of view of Supercollider is completed mistaken.

Its not cause most of the code you find is ugly, that the language is ugly.

Actually from all the languages you were able to link in your email,
SuperCollider is probably the one that lets you do the most beautiful code,
its all about how capable you're.


good luck

On 5 December 2012 22:24, Kassen <signal.automatique at gmail.com> wrote:

> On Wed, Dec 05, 2012 at 02:51:58PM -0500, Rob Fielding wrote:
> > 1) The GPL licensing (SuperCollider as well as ChucK) seems to be an
> issue
> > for anyone trying to host ChucK embedded into a controller process.  Is
> > this an actual problem, given that we are generally just linking in
> > unmodified build of the sources?
>
> IANAL, this is not legal advice, I don't represent the ChucK team on
> this matter.
>
> As long as your controller process has a compatible license and you
> also share the code all should be fine. If not there may be a problem
> but I think that only starts to matter when you would distribute the
> combined work. Between GPL-ed programs you can freely borrow/port.
> That is very convenient for those projects.
>
> If that is not practical for you I think you can legally have your
> closed source program communicate with ChucK, redistribute ChucK with
> your program and add the ChucK source to that.
>
> What you can not do is take GPL software and use it as a part of your
> closed project, then sell or otherwise redistribute the result without
> the source. If that is what you want/need something like PD which has
> a far more liberal license might be what you are after. Personally I
> like the GPL, I think it encourages a kind of sharing that benefits
> all.  Evidently many other people, like some groups developing stuff
> for mobile devices enjoy borrowing PD's source which PD's BSD licence
> allows.
>
> You should probably consider what your needs are with regard to
> distribution, how closely coupled the synthesis engine and the
> controlling process need to be and where you stand on this kind of
> sharing here. If in doubt after a closer reading of the GPL you might
> want to consult a lawyer. I'd avoid a legal fight, both because those
> are no fun and because ChucK comes from Princeton and Stanford.
>
> I hope that clarified things a bit and that I didn't misrepresent
> something. I also hope you will make a Free/Open instrument, I think
> sharing is fun, but that is up to you and might not be practical in
> your situation.
>
> Yours,
> Kas.
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20130212/5789f212/attachment.html>


More information about the chuck-users mailing list