I wish this was possible. AFAIK, iOS only supports frameworks shipped by Apple itself. You cannot create your own framework for and link it dynamically. I know this is different in OSX, but iOS is a different beast. :(<div>
<br></div><div>- Ragi<br><br><div class="gmail_quote">On Wed, Apr 20, 2011 at 7:07 AM, William Kyngesburye <span dir="ltr"><<a href="mailto:woklist@kyngchaos.com">woklist@kyngchaos.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Apr 19, 2011, at 7:01 PM, Ragi Burhum wrote:<br>
<br>
> Sorry about bringing a licensing question, but I am curious.<br>
><br>
> I know the implications of using LGPL code in shared libraries (on "traditional" apps), so no need to explain it there.<br>
><br>
> However, I am curious as to the iOS case, where every app *has* to be statically linked. I know there are apps out there that have been compiled with Spatialite support (with GEOS option on), but the code for those apps are nowhere to be found. Is it because they are violating the LGPL, or is there some other way to link to GEOS without having to release all of your code under GPL terms.<br>
><br>
</div></div>If an iOS app must statically link *libraries*, use a framework so it can be dynamically linked. I have a GEOS framework package for OS X, and a build script that could be adapted to create an iOS version.<br>
<br>
-----<br>
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com><br>
<a href="http://www.kyngchaos.com/" target="_blank">http://www.kyngchaos.com/</a><br>
<br>
[Trillian] What are you supposed to do WITH a maniacally depressed robot?<br>
<br>
[Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer...<br>
<br>
- HitchHiker's Guide to the Galaxy<br>
<br>
<br>
</blockquote></div><br></div>