BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Library GPL

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (Non-Technical)
View previous topic :: View next topic  
Author Message
Jonathan Benedicto
Guest





PostPosted: Tue Nov 15, 2005 4:23 pm    Post subject: Library GPL Reply with quote



I was reading through the Library GPL, as one of my classes is using a
Library GPL'ed library, and I just wanted someone to help clarify what the
Library GPL requires from me to be able to use it in commercial programs.
Eg, do I have to release my code.

Jonathan


Back to top
Duane Hebert
Guest





PostPosted: Tue Nov 15, 2005 7:21 pm    Post subject: Re: Library GPL Reply with quote




"Jonathan Benedicto" <incorrect (AT) no (DOT) server> wrote

Quote:
I was reading through the Library GPL, as one of my classes is using a
Library GPL'ed library, and I just wanted someone to help clarify what the
Library GPL requires from me to be able to use it in commercial programs.
Eg, do I have to release my code.

There are some different levels of GPL. There's LGPL for example that
allows
you to get away with a bit. Typically, GPL requires making your code
available
but again, it depends. Best to read the specific one or post here the
section
that you don't understand.


Back to top
Jonathan Benedicto
Guest





PostPosted: Tue Nov 15, 2005 7:33 pm    Post subject: Re: Library GPL Reply with quote



Duane Hebert wrote:
Quote:
There are some different levels of GPL. There's LGPL for example
that allows you to get away with a bit. Typically, GPL requires
making your code available but again, it depends. Best to read
the specific one or post here the section that you don't understand.

Thank you, well here is the section. I wish that licences were written in a
little more friendly form. <g>

5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also compile or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

....

This seems to indicate that I can't use a Library GPL'ed library, even when
dynamically linked without providing either the objs or the .cpp's.

Jonathan



Back to top
Duane Hebert
Guest





PostPosted: Tue Nov 15, 2005 9:52 pm    Post subject: Re: Library GPL Reply with quote


"Jonathan Benedicto" <incorrect (AT) no (DOT) server> wrote


Quote:
This seems to indicate that I can't use a Library GPL'ed library, even
when
dynamically linked without providing either the objs or the .cpp's.

It sounds like that's the case. It sounds like you can write a library that
can
be linked with their library by another application without dealing with the
license
but if you have any compiled code that does use it, then you're bound by the
license.
I'm not a lawyer though.
One thing that sometimes works is to contact the owner
of the license with a specific question.


Back to top
Jonathan Benedicto
Guest





PostPosted: Tue Nov 15, 2005 9:58 pm    Post subject: Re: Library GPL Reply with quote

Duane Hebert wrote:
Quote:
One thing that sometimes works is to contact the owner
of the license with a specific question.

Thank you, I'll do this.

Jonathan



Back to top
Micha Nelissen
Guest





PostPosted: Wed Nov 16, 2005 9:01 pm    Post subject: Re: Library GPL Reply with quote

On Tue, 15 Nov 2005 14:33:07 -0500
"Jonathan Benedicto" <incorrect (AT) no (DOT) server> wrote:

Quote:
This seems to indicate that I can't use a Library GPL'ed library, even when
dynamically linked without providing either the objs or the .cpp's.

The idea is basically that either:
1) you link dynamically to .dll, and you only provide the sources of the
library (if asked for), but not for your application
2) you link the library statically into your app, then you need to provide
the .obj's of your application with a linker script to be able to regenerate
the executable with a new (possibly) patched version of the library.

HTH,

Micha

Back to top
Jonathan Benedicto
Guest





PostPosted: Wed Nov 16, 2005 10:35 pm    Post subject: Re: Library GPL Reply with quote

Micha Nelissen wrote:
Quote:
The idea is basically that either:
1) you link dynamically to .dll, and you only provide the sources of
the library (if asked for), but not for your application
2) you link the library statically into your app, then you need to
provide the .obj's of your application with a linker script to be
able to regenerate the executable with a new (possibly) patched
version of the library.

Ok, thank you. That makes sense. I wish that these licences were not so
complicated.

Jonathan



Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (Non-Technical) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.