[Cs-dev] iOS linking and C api
Date | 2012-04-27 20:32 |
From | Casey Basichis |
Subject | [Cs-dev] iOS linking and C api |
Attachments | None None |
Hi,
Its been almost a decade since I last dipped my toes in to the csound. Is the iOS port setup to handle the obj. file creation and linking so the app can be distributed in the AppStore?
Is it possible to access the C api in the same way, or does that dismantle the idea of linking to objects in the first place? I'm very new to all of this. I half know what half of this means. I would really like to use csounds vast processing in my application, but I'm wary of inadvertently encompassing the whole thing into a gpl death pit.
Does anyone have any experience with cSound in iOS that could lend their experience? Thanks, Casey
|
Date | 2012-04-27 21:25 |
From | Steven Yi |
Subject | Re: [Cs-dev] iOS linking and C api |
HI Casey, Csound is LGPL, so you'll have to follow that license if you use it. On iOS, since it is static linking only, it means you should be providing the source code to your application if you publish one using Csound. This is applies to all applications that statically link to Csound, desktop or otherwise. Otherwise, the process for building apps is fairly straightforward. The iOS SDK has an example application and a manual that explains usage. You can access the C API or use the Obj-C API (called CsoundObj). Creating new apps with Csound for iOS generally just starts off with creating the application, the adding the csound-iOS folder to your application, which has headers, .a libs, and obj-c files for Csound. After that, you can compile and deploy to simulator or device. Hope that helps! steven On Fri, Apr 27, 2012 at 8:32 PM, Casey Basichis |