[Stk] iOS static library

[Aran Mulholland]

Any chance it could be a cocoa pod?


On Wed, Mar 5, 2014 at 5:17 AM, Perry R Cook <prc at cs.princeton.edu> wrote:

> Yay!!  Then it seems we have a pretty good solution.
> Save for the waiting for a clean and build, building
> the whole library seems like the best way.  Then
> naive programmers don't have to do lots of inheritance
> traversing to see what to compile, (just includes in
> their own code).
>
> This is really great!  Thanks for doing this all.
>
> PRC
>
> ----- Original Message -----
> ..
>
> Unless gcc/Xcode is really dumb (which I don't think it is), it will not
> link the whole of a static library with an app regardless - only the
> functions the app actually uses, i.e. the linker does the cherry-picking
> itself. The linker/compiler also does a standard "dead code elimination"
> step when compiling/optimising, so even the code you have written in the
> app but which never gets called is also excluded. So I just built  the
> whole of the stk as a static library (minus the redundant bits such as
> direct audio i/o). So - my stk static library runs out at some 9MB, but
> my test iOS app, which uses only a small part of it, is under 500K.
>
> Richard Dobson
>
> _______________________________________________
> Stk mailing list
> Stk at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/stk
>
> _______________________________________________
> Stk mailing list
> Stk at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/stk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ccrma-mail.stanford.edu/pipermail/stk/attachments/20140306/434a27a4/attachment.html