<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
From: Greg Troxel <<a href="mailto:gdt@ir.bbn.com">gdt@ir.bbn.com</a>><br>
Subject: Re: [geos-devel] licensing when doing a static link of GEOS<br>
in iOS<br>
To: Sandro Santilli <<a href="mailto:strk@keybit.net">strk@keybit.net</a>><br>
Cc: GEOS Development List <<a href="mailto:geos-devel@lists.osgeo.org">geos-devel@lists.osgeo.org</a>><br>
Message-ID: <<a href="mailto:rmiei4xi0hm.fsf@fnord.ir.bbn.com">rmiei4xi0hm.fsf@fnord.ir.bbn.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
<br>
Sandro Santilli <<a href="mailto:strk@keybit.net">strk@keybit.net</a>> writes:<br>
<br>
> On Tue, Apr 19, 2011 at 05:01:39PM -0700, Ragi Burhum wrote:<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<br>
>> "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<br>
>> statically linked. I know there are apps out there that have been compiled<br>
>> with Spatialite support (with GEOS option on), but the code for those apps<br>
>> are nowhere to be found. Is it because they are violating the LGPL, or is<br>
>> there some other way to link to GEOS without having to release all of your<br>
>> code under GPL terms.<br>
><br>
> Distributing a binary version of GEOS (statically linked, in this case)<br>
> w/out distributing also the source code (of GEOS) is a clear license<br>
> violation.<br>
><br>
> Section 6 of the LGPL text cover this.<br>
> <a href="http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html" target="_blank">http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html</a><br>
><br>
> If I recall correctly Apple forbids distributing source code trough<br>
> the apple store, which was the reason for VLC being dropped from there.<br>
> Apple devices are well known for being defective by design<br>
> <a href="http://www.defectivebydesign.org" target="_blank">http://www.defectivebydesign.org</a><br>
<br>
Further, my understanding (IANAL) is that the app store terms of service<br>
forbid the user to redistribute, and that's incompatible with all<br>
copyleft licenses (the "any other restriction" clause), even if you did<br>
provide source and dynamic linking with LGPL. So as far as I can tell,<br>
it's improper to include any GPL/LPGL code in any iOs app, period.<br>
<br>
Please do name the apps that seem to do this.<br></blockquote><div><br></div><div>Upon further reading, I stumbled upon this <a href="http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/">http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/</a></div>
<div>It seems that app developers have a choice to provide .o and .a files to be able to relink without providing source code?? I guess that would make it feasible to use 3rd party proprietary (where no source code is available) SDKs.</div>
<div><br></div><div>As far as naming those apps explicitly, there are various GPS apps in the appstore that use spatialite, but without jailbreaking my phone, downloading the apps and dumping symbols from the binaries, I would be hesitant to make any accusation based on comments I heard from word of mouth :(</div>
<div><br></div><div>- Ragi</div></div>