[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Licensing issues with a research project
From: |
John Hasler |
Subject: |
Re: Licensing issues with a research project |
Date: |
Tue, 11 Aug 2009 07:39:04 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Tassilo writes:
> Our lib is GPL and it has a code generator which spits out java code.
> The generated code is also GPLed currently, and the EPL code
> specializes the generated classes only. Could we change our lib to
> LGPL and spit out BSD-style licensed code, so that the library itself
> is only used/linked and only the generated code is extended/modified?
Does the generated code contain significant fractions of protected
elements of the library itself? If not the generated code is a
mechanical transformation of the input and so only the license on the
input applies. Even if elements of the library are in the generated
code you can apply a different license to them than to the library. The
Gcc license does exactly that.
--
John Hasler
john@dhh.gt.org
Dancing Horse Hill
Elmwood, WI USA
- Licensing issues with a research project, Tassilo Horn, 2009/08/10
- Re: Licensing issues with a research project, Alexander Terekhov, 2009/08/10
- Message not available
- Re: Licensing issues with a research project, John Hasler, 2009/08/11
- Re: Licensing issues with a research project, Alexander Terekhov, 2009/08/11
- Re: Licensing issues with a research project, Tassilo Horn, 2009/08/11
- Message not available
- Re: Licensing issues with a research project, Alexander Terekhov, 2009/08/11
- Re: Licensing issues with a research project, Tassilo Horn, 2009/08/12
- Message not available
- Re: Licensing issues with a research project, Alexander Terekhov, 2009/08/12
- Message not available
- Re: Licensing issues with a research project, John Hasler, 2009/08/11