如果要求在iPhone应用程序中遵守LGPL，我需要分发什么文件？ [英] What files do I need to distribute if requested to comply with LGPL in an iPhone app?

问题描述

我正在使用一个iPhone应用程序，它使用ZGB库的LGPL许可证。我想知道的是，如果他们请求我的iPhone应用程序的许可证下的代码副本，我需要什么？

I'm working on an iPhone app which uses the Zbar library which is under the LGPL licence. What I'd like to know is what I need to give someone if they request a copy of the code under this licence for my iPhone app?

我被告知它们在build文件夹中，并且它们是.o文件。我发现了一些在armv6和armv7文件夹，以及一个LinkFileList和什么看起来像我的应用程序名称的终端应用程序。我只是在我的源文件之一，我的UIViewControllers之一使用库。

I've been told they are in the build folder and also that they are .o files. I've found some of those in the armv6 and armv7 folders along with a LinkFileList and what looks like a terminal app with my app name. I only use the library directly in one of my source files, one of my UIViewControllers.

有人可以告诉我，我需要发送他们所有这些文件或只是特定的？我也在日志中引用了一个链接命令，但不知道这是在哪里。

Can someone please tell me, do I need to send them all these files or just specific ones? I was also referred to a link command in a log but don't know where this is.

谢谢。

推荐答案

我很确定没有办法遵守标准LGPL与iPhone。有些使用LGPL的项目已经为iPhone制作了特殊条款。

I am pretty sure that there is no way to comply with a standard LGPL with iPhone. Some projects with LGPL have been making a special clause for iPhone.

这是我的推理（但我不是专家或律师）。 LGPL的目的是，您可以制作使用开源库的商业产品，只要用户只能更新库，您的程序将使用它。这是大多数子句背后的推理，它们需要动态链接到库以确保。

Here is my reasoning (but I am not an expert or lawyer). The purpose of LGPL is that you can make commercial products that use the open-source library as long as a user can update just the library and your program will use it. That is the reasoning behind most of the clauses and they require dynamic linkage to the library to assure that.

但是，Apple不允许在iPhone应用程序中动态链接，除了包括的库 - 如果你尝试使用.dylib，你会被拒绝。此外，即使你可以使用dylib，也没有办法让最终用户更新它 - 它的来源并不好。

But, Apple doesn't allow dynamic linkage in iPhone apps except to the included libraries -- if you try to use a .dylib, you will be rejected. Furthermore, even if you could use a dylib, there is no way for the end user to update it -- having the source does them no good.

这里有一些讨论：

哪些开源许可证与Apple的iPhone及其官方App Store兼容？

根据我的看法， '需要使所有的.o文件从您的源可用 - 我仍然认为这可能不满足所有的要求，因为没有办法为最终用户得到他们的iPhone，除非他们有一个开发人员许可证。

According to what I see, you'd need to make all of the .o files built from your source available -- I still think this might not meet all of the requirements because there is no way for the end-user to get them to the iPhone unless they have a developer license.

如果你认为.o文件就足够了，那么你必须提供所有的文件，而不仅仅是使用库的文件。他们需要替换库 - 所以对于非动态链接，他们需要应用程序的所有.o文件。

If you think .o files are enough, then you must provide all of them, not just the one that uses the library -- they are supposed to have everything they need to replace the library -- so for non-dynamic linkage, they need all of the .o files for the app.

更新：我对这个更多的想法这里

Update: I put more thoughts about this here

http://www.loufranco.com/blog/files/lgpl-and-the-iphone.html

我写信给GNU for a澄清，但我相信苹果的条款暗示，LGPL不能使用（因为他们收取任何人实际做更新，并且许可证要求不收取行使权利）

I wrote to GNU for a clarification, but I believe that Apple's terms imply that the LGPL cannot be used (since they charge anyone to actually do the update, and the license requires no charge to exercise rights)

这篇关于如果要求在iPhone应用程序中遵守LGPL，我需要分发什么文件？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！