Winelib 可以与商业应用程序一起使用吗？
这是我可以问这个问题的唯一地方，因为 WineHQ 论坛由于某种原因被锁定......所以请告诉我是否可以将 Winelib 与商业应用程序静态链接它的使用条款是什么？是否应该在文档、应用程序的“关于”框中等中予以确认？
This is the only place I can ask this question since the WineHQ forum is locked for some reason... So please tell me if I can statically link Winelib with a commercial application and what are the terms of its use - should it be acknowledged in documentation, application's about box, etc.?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
几点：
你不能真正静态地链接到 Winelib。我的意思是 - 你可能可以，但无论如何你仍然需要几乎所有 Wine 的基础设施。 Winelib 是 Wine 的 95%，基本上是减去 PE-Loader（可以读取 Windows 可执行文件的代码）的所有内容。
Wine 已获得 LGPL 许可。 IANAL，但这意味着您可以将 Wine 与您的商业应用程序一起分发，而不必被迫开源您自己的代码。它的工作原理如下：当您将您的应用程序与 Wine 结合时，您创建了一个派生作品（或您的应用程序和 Wine）。 GPL 要求自由软件的派生作品也是自由软件，而 LGPL 则不然。尽管如此，如果您修改 Wine 代码以使其与您的应用程序兼容，您需要将修改后的 Wine 源代码提供给您分发产品的人员。该许可证列出了有关如何遵守源代码要求的多个选项。
无论您的应用提供自己的许可信息，您都需要向 LGPL 添加通知。阅读 LGPL 了解详细信息。
A couple of points:
You can't really link with Winelib statically. I mean - you probably can, but it you still need almost all of Wine's infrastructure, anyway. Winelib is 95% of Wine, basically everything minus the PE-Loader (the code that can read Windows executables).
Wine is licensed LGPL. IANAL, but that means you can distribute Wine with your commercial app without being forced to open-source your own code. It works as follows: When you combine your app with Wine you create a derived work (or your app and of Wine). The GPL requires a derived work of free software to be free software as well, the LGPL does not. Still, if you modify Wine-code to make it work with your app, you need to make the modified Wine source available to the people you distribute your product to. The license lists several options on how to comply with the source code requirement.
You need to include a notice to the LGPL wherever your app provides its own licensing information. Read the LGPL for the details.