从LGPL许可下的库继承一个类。这可以吗 ？

问题描述

大家好。



我有一个LGPL许可的图书馆。

并希望我的申请成为封闭源和商业项目。

所以我不会修改原来的LGPL库的代码，

但我会链接LGPL lib（通过DLL文件），然后继承它的主类到来自我的闭源项目的一个新的，只修改我的项目的新继承类。



我从LGPL许可证中了解到我需要发布来自LGPL库的修改代码。这就是为什么我想继承它的代码然后才改变它，所以我想问你这是否公平和好，因为它可能违反了这个许可证的主要思想。给所有想要使用它的人免费提供它的源代码。



另外，如果我使用LGPL，我想问你到底需要做什么图书馆。



我明白我需要留下LGPL库的源代码（带我的应用程序）

并给出一个链接和信用等。



对不起我的英文错误，我将感谢您的任何更正。

并感谢大家阅读我的问题。

解决方案

Hello everyone .

I have a library which is under LGPL license .
And want my application to be a closed-source and commercial project .
So i will not modify the original LGPL library's code ,
But i will link the LGPL lib (via DLL file) and then inherit it's main class to a new one from my closed-source project and only than modify the new inherited class for my project .

And i understood from the LGPL license that i need to publish the modified code from the LGPL library . That is why i want to inherit its code and only then change it , so i want to ask you if this is fair and OK , because maybe its against the main idea of this license . to leave it's source code free to everyone who want to use it .

Also , I wanted to ask you what exactly i need to do in addition if i use a LGPL library .

I understood that i need to leave there a source code of the LGPL library (with my application)
and also give a links and credits etc .

Sorry for my English mistakes , I will thank for any corrections .
and thanks everyone for reading my questions .

解决方案

这篇关于从LGPL许可下的库继承一个类。这可以吗 ？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！