Re: Using GPL libraries
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Fri, 02 Dec 2005 00:13:48 -0500
Not really. The DLL source code would be open code, but you can distribute an app and
distribute a DLL which is completely separate from the app. At least one of my clients
did serious research on this and that was the word he got.
Actually, my view is that the GPL has actually done more harm than good. All it does is
mean that anything under the GPL is unusable in products, and that is counterproductive.
On the whole, I avoid GPL components. They do me no good whatsoever, because I work with
people who do not want to make their complete source visible.
joe
On Wed, 30 Nov 2005 09:23:42 +0800, Jonathan Wilson <jonwil@xxxxxxxxxxx> wrote:
>Joseph M. Newcomer wrote:
>
>> Simple answer: yes.
>> More complex answer: if you use the library solely as a DLL and do not link it directly
>> into your app, it appears you do not. Otherwise, you cannot use a GPL library in your
>> product without being in violation of the terms of the GPL.
>Actually, you need to distribute the full source code even if you are just
>linking to the GPL library as a DLL.
>
>There is also the LGPL which is different.
Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Prev by Date: Re: Setwindowpos()-problem.Moving control is not happening.
- Next by Date: Re: cannot catch exception
- Previous by thread: Re: Using GPL libraries
- Next by thread: A couple of questions
- Index(es):
Relevant Pages
|
