This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Question about libgcj license and header file inclusion
- From: Bryce McKinlay <mckinlay at redhat dot com>
- To: Jeremy Felix <Jeremy dot Felix at codegreennetworks dot com>
- Cc: java at gcc dot gnu dot org
- Date: Wed, 29 Mar 2006 17:39:13 -0500
- Subject: Re: Question about libgcj license and header file inclusion
- References: <90EB1A0E97FA824CA5C08B05AFF679525EF72E@SBS.codegreennetworks.com>
Jeremy,
I believe the intent of the license is certainly to allow that. The
Classpath/libgcj exception statement was written with Java code in mind,
so it does not explicitly mention C headers like the libstdc++ one does.
However, I would consider #including a header in C to be equivalent to
importing a class in Java, thus it is covered under the linking
exception clause.
If you want more clarification you could try asking this question on the
Classpath list (classpath@gnu.org)
Regards,
Bryce
Jeremy Felix wrote:
Iâve been reading through the LIBGCJ_LICENSE file as well as the GNU GPL, and I have a question about including header files with this license in proprietary modules. Can one include headers with this license in a proprietary module without making the module GPL? Specifically, can one include jni.h from a proprietary C module? There is no explicit clause that I could see which would permit this, which is different from the libstdc++ exception.
Forgive me if this has already been answered elsewhere.
Thanks in advance,
Jeremy Felix