Re: [Cs-dev] iOS linking and C api
Date | 2012-04-28 22:49 |
From | Casey Basichis |
Subject | Re: [Cs-dev] iOS linking and C api |
Attachments | None None |
Thanks for the info. From what I have read, its possible, as an alternative to releasing the full source, the main app can be compiled into libraries and linked to the lgpl code, and then provided as objects with an xcode file in order link to any newer version of the lgpl code. Is there anything in particular about the csound implementation that would make that route untenable?
Time to dust off the old csound book
|
Date | 2012-04-28 23:33 |
From | Steven Yi |
Subject | Re: [Cs-dev] iOS linking and C api |
Hi Casey, Yes, there seems to be that clause in the LGPL. I found this just now: http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/ So .a/.o publishing should be a possibility. However, I am not a lawyer, but seems right to me, and I'm not aware of anything unique to Csound or libsndfile that would make that untenable. One other note, one should also post the LGPL license in the application. I am not sure if that needs to be done twice, once for libsndfile and another for Csound, or if you can just post it once and say both parts are licensed under the same license (they're both LGPL v2.1). Regardless, once you get started, feel free to ask any questions you may have here. Hopefully the manual and example project that comes with the Csound iOS SDK will give you a good place to start. Enjoy! steven On Sat, Apr 28, 2012 at 10:49 PM, Casey Basichis |