IANAL, but AFAIU you would be linking against LGPL libraries. So you can use a proprietary product with them fine, so long you provide to the user of your apps any modification that you did to the LGPL code that you used. (MonoMac is Apache/MIT so no problem there either.)
The only problem you would have is if you link to GPL libraries and you don't want to make your app GPL as well (the only ones licensed as GPL are the Mono tools... not sure if mkbundle is one of them but if you just use it to generate your executable, and you don't link to it in any way afterwards, I guess you're fine.)
Anyway, better to do as Strillo says, just in case.
发布评论
评论（2）
您可以此处联系 Xamarin，并与他们核实您是否需要商业许可证。
You can contact Xamarin here and check with them whether you need a commercial license.
看看这个。
IANAL，但 AFAIU 您将链接到 LGPL 库。因此，只要您向应用程序的用户提供对所使用的 LGPL 代码所做的任何修改，您就可以很好地使用专有产品。 （MonoMac 是 Apache/MIT，所以那里也没有问题。
）如果您链接到 GPL 库并且您不想让您的应用程序也成为 GPL（唯一获得 GPL 许可的是 Mono 工具...不确定 mkbundle 是否是其中之一，但如果您只是使用它生成您的可执行文件，并且之后你就不会以任何方式链接到它，我想你没问题。）
无论如何，最好按照斯特里洛的说法去做，以防万一。
Take a look at this.
IANAL, but AFAIU you would be linking against LGPL libraries. So you can use a proprietary product with them fine, so long you provide to the user of your apps any modification that you did to the LGPL code that you used. (MonoMac is Apache/MIT so no problem there either.)
The only problem you would have is if you link to GPL libraries and you don't want to make your app GPL as well (the only ones licensed as GPL are the Mono tools... not sure if mkbundle is one of them but if you just use it to generate your executable, and you don't link to it in any way afterwards, I guess you're fine.)
Anyway, better to do as Strillo says, just in case.