Well, what in the JSC distribution (files) are you modifying? Licenses only cover files. LGPL does not impose a license on your code, just the LGPL code. If you modify the LGPL code you must distribute that. If you add-on in a way that does not modify the original LGPL code. Then you are fine. Even if your QtDeclaritive additions modify the JSC, you would not have to distribute your whole app, just the modified parts of JSC.
GPL imposes itself on your code. I've heard that static linking to GPL is probably a license violation (without distributing) while LGPL code is just fine. It'd cease to be LGPL and be GPL otherwise. ----- Original Message ---- From: Stephen Kelly <[email protected]> To: [email protected] Sent: Tue, March 1, 2011 4:51:20 AM Subject: Re: [Qt-qml] QML and LGPL? Jason H wrote: > In my experience LGPL only applies when you change the files in the > library not add on to it. > If someone adds a QML object, how does that change what was under the LGPL > license? > You're not modifying LGPL files are you? It sees your distinction would > obliterate the differences between GPL and LGPL. > Well your understanding doesn't match mine at all, so certainly one of us is misunderstanding :). Here's my reasoning: * The LGPL gives you certain rights to distribute the covered software. * JavaScriptCore is covered by the LGPL. * When you distribute JSC in source or binary form, you do so under the terms of the LGPL. * When you distribute an app that uses QtQuick, either by statically or dynamically linking to QtScript/QtDeclarative or by distributing a statically or dynamically compiled qmlviewer along with some QML files, you distribute the JSC part along with it. Your distribution of JSC is allowed by the LGPL subject to the terms of the licence. * If you modify JSC, your modifications to JSC must be made available to downstreams in compliance with the LGPL. * Everything 'above' JSC you can either get a licence for (Qt, other third party software), or write yourself. The LGPL doesn't affect those in any other way. That is, any distibution of the LGPL-covered work needs to be done under the terms of the LGPL. That might mean you have to include the licence text and a means of allowing your downstreams to download the JSC source. It might even mean that if you link statically to Qt, you might have to link dynamically to JSC somehow. I don't know if that's possible. You would have to ask a lawyer about what the licence really means. Obviously I am not one. All the best, Steve. _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
