Monte Goulding wrote:
On 01/08/2013, at 12:31 AM, Richard Gaskin <ambassador at fourthworld.com>
wrote:
GPL3 distinguishes "dynamic linking" as not affected, while "static linking"
explicitly inherits GPL freedoms.
I thought it was LGPL that made that distinction.
On further review, I believe you're right. I got hung up on the phrase
"dynamically linked", having glossed over the rest of this clause from
Section 1 of GPL3:
The “Corresponding Source” for a work in object code form means
all the source code needed to generate, install, and (for an
executable work) run the object code and to modify the work,
including scripts to control those activities. However, it does
not include the work's System Libraries, or general-purpose tools
or generally available free programs which are used unmodified in
performing those activities but which are not part of the work.
For example, Corresponding Source includes interface definition
files associated with source files for the work, and the source
code for shared libraries and dynamically linked subprograms
that the work is specifically designed to require, such as by
intimate data communication or control flow between those
subprograms and other parts of the work.
That last sentence seems less about whether it's statically or
dynamically linked, and more appropriately (it seems to me) about the
degree to which such files are essential to the core functionality of
the work.
Thanks for prompting my re-read (so much falls out of one's head after a
few days in Hawaii <g>).
--
Richard Gaskin
Fourth World Systems
Software Design and Development for Desktop, Mobile, and Web
____________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
