Используя GPL v2 DLL в [закрытом] приложении
- Общее Владение
- повышение:: shared_ptr
, Когда ресурс совместно используется несколькими объектами. Повышение shared_ptr использует подсчет ссылок, чтобы удостовериться, что ресурс освобожден, когда все - finsihed.
2 ответа
I found an interesting post on this:
Does the use of GPL'ed DLLs from the GnuWin32 project in your program need you to release your program under GPL too?
There seem to be two different strands of opinion. The FSF holds that dynamic linking creates a derivative work, and so any program designed to run with a GPL-ed DLL, must be GPL itself; see http://www.fsf.org/licenses/gpl-faq.html. The only exception they make is for DLL's that come with the compiler and the kernel, such as the MS VC run-time DLL's; see http://www.fsf.org/licenses/gpl-faq.html#WindowsRuntimeAndGPL. On the other hand some OpenSource lawyers hold that dynamically linking does not make your program GPL. See http://www.nusphere.com/products/library/gpl_0401openmag.pdf and the discussion in http://www.linuxjournal.com/article.php?sid=6366. There is no doubt that programs that link dynamically to DLL's from libraries with the LGPL or with the GPL with special provisions, are GPL free if you decide so.
If you link to a GPL v2 dll and distribute that program, you will have to make your source code available as GPL v2/3.
See http://www.opensource.org/licenses/gpl-2.0.php. The paragraph at the bottom mentions LGPL if linking is allowed without having to make your code GPL-licensed and it also says:
This General Public License does not permit incorporating your program into proprietary programs