From: Hansi R. <su...@su...> - 2010-12-01 20:18:08
|
hey! > ok, guys, the generated code of gcc, bison, xmlvm do not fall under GPL > or L-GPL. The clarification for bison is that since there is a bit of > library portion that needs to be linked against the generated code > automatically makes the whole application GPL (note that bison is GPL, > not L-GPL). Since xmlvm is licensed under L-GPL, this problem does not > occur. i agree to 99%. the 1% i don't agree on is for instance the file "Application.js.template" that is part of xmlvm (thus lgpl): to make my point clear let me quote the file here: /* ************************************************************************ #asset(temp_qx_app/*) ************************************************************************ */ /** * This is the main application class of your custom application "temp_qx_app" */ qx.Class.define("{{XMLVM_TEMP_PROJECT_NAME}}.Application", { extend : qx.application.Standalone, members : { main : function() { // Call super class this.base(arguments); // Enable logging in debug variant if (qx.core.Variant.isSet("qx.debug", "on")) { // support native logging capabilities, e.g. Firebug for Firefox qx.log.appender.Native; // support additional cross-browser console. Press F7 to toggle visibility qx.log.appender.Console; } {{XMLVM_MAIN_METHOD_CALL}} } } }); this is lgpl code and the transformed code is copied into it, which imho is a modification (not inheritance or linking) of the original code, and should thus be made available under the lgpl as well. i might be wrong about this and as long as the intentions of the project are clear this is not going to be a problem at all. best, hansi. |