Comments on: Compatibility between the iPhone App Store and the LGPL http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/ Explorations in Social Computing Fri, 17 Jun 2011 14:33:00 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Thomas Shin http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/comment-page-1/#comment-119 Thomas Shin Fri, 11 Dec 2009 21:13:16 +0000 http://multinc.com/?p=157#comment-119 Hi, I'm trying to contact the author of this blog for a possible software dev commission and support on a previous project. However, I can't find any of your contact information, email address, etc. Please contact me at your earliest possible convenience. Hi, I'm trying to contact the author of this blog for a possible software dev commission and support on a previous project. However, I can't find any of your contact information, email address, etc. Please contact me at your earliest possible convenience.

]]> By: huyzing http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/comment-page-1/#comment-114 huyzing Fri, 04 Sep 2009 02:16:38 +0000 http://multinc.com/?p=157#comment-114 As Pierre said on <a href="http://www.nabble.com/Re%3A-iphone%2C-and-releasing-object-code-satisfies-LGPL-Re%3A-Static-building-and-bundling-of-SDL.-p21920761.html" rel="nofollow">Nabble</a><br><br><blockquote>Or you could do like id<br>Software did with Quake3 (and possibly their other games), only really<br>protect the resource file and distribute the binaries willy-nilly. </blockquote><br><br>I guess it all depends on the level of risk you want to accept. As Pierre said on Nabble

Or you could do like id
Software did with Quake3 (and possibly their other games), only really
protect the resource file and distribute the binaries willy-nilly.

I guess it all depends on the level of risk you want to accept.

]]> By: benclayton http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/comment-page-1/#comment-112 benclayton Thu, 27 Aug 2009 11:06:50 +0000 http://multinc.com/?p=157#comment-112 This is the best write-up of this thorny issue I've yet seen on the interweb, so thanks!<br>I didn't realize that the option of distributing the .a and .o files was available either to iPhone devs. Does this mean though that anyone who did download your object files could link parts of your app (say, a particularly cool module you'd written) into their own? Seems quite risky. Also, wouldn't you need to distribute all of the resource files too? (graphics, audio etc) - eek! <br>It seems likely that problems of this kind will simply have the effect of making LGPL licensing of iPhone-specific components less prevalent. Of course there's still mountains of platform-independent LGPL code out there that's presumably now best avoided.. :-( This is the best write-up of this thorny issue I've yet seen on the interweb, so thanks!
I didn't realize that the option of distributing the .a and .o files was available either to iPhone devs. Does this mean though that anyone who did download your object files could link parts of your app (say, a particularly cool module you'd written) into their own? Seems quite risky. Also, wouldn't you need to distribute all of the resource files too? (graphics, audio etc) – eek!
It seems likely that problems of this kind will simply have the effect of making LGPL licensing of iPhone-specific components less prevalent. Of course there's still mountains of platform-independent LGPL code out there that's presumably now best avoided.. :-(

]]>