Re: Separate csharpcomp.sh, and a license problem

[Simon Josefsson]

Bruno Haible <address@hidden> writes:

> I agree with all this. I've changed gnulib-tool to accept modules whose
> license is "GPLed build tool", and created a csharpcomp-script and
> javacomp-script module under this license. This should make it clear
> that - unlike the automake-provided build tools but exactly like
> texinfo.tex - the tool is GPL but its use as build tool does not
> infect your source with GPL.

Thanks!

>       * modules/csharpcomp: Depend on it.
>       * modules/javacomp: Depend on it.

These two patches were forgotten, apparently.

I'm now using csharpcomp to build the Libidn C# port.

How does javacomp relate to the automake Java support?  The Java port
of Libidn currently use the Java support in automake.  This feels more
"right" to me, even if the M4 macros to find gcj/jar are poorly
written and not part of autoconf/automake.  How about merging the
javacomp script with automake?  That would make it possible to use
non-gcj java compilers too.  If that is done, perhaps also supporting
C#, through csharpcomp, in automake is simple.

Thanks,
Simon