Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> How would build-aux/ be substituted into $auxdir? Should gnulib-tool
>> substitute 'build-aux/' in configure.ac:-statements to $auxdir?
>
> I committed this patch.
Works fine, thanks!
However, I'm wondering whether:
AC_CONFIG
Simon Josefsson wrote:
> AC_CONFIG_FILES([csharpcomp.sh:build-aux/csharpcomp.sh.in])
>
> is the best default. It seem to cause csharpcomp.sh to end up in the
> top-level directory. I don't like this.
libtool does the same.
Bruno
___
bug-gnulib mai
Simon Josefsson wrote:
> How would build-aux/ be substituted into $auxdir? Should gnulib-tool
> substitute 'build-aux/' in configure.ac:-statements to $auxdir?
I committed this patch.
2006-01-11 Bruno Haible <[EMAIL PROTECTED]>
* gnulib-tool (func_import, func_create_testdir): Replace
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> How would build-aux/ be substituted into $auxdir? Should gnulib-tool
>> substitute 'build-aux/' in configure.ac:-statements to $auxdir?
>
> Yes, it should. I'll prepare a patch for doing this.
That would solve this problem. I
Simon Josefsson wrote:
> How would build-aux/ be substituted into $auxdir? Should gnulib-tool
> substitute 'build-aux/' in configure.ac:-statements to $auxdir?
Yes, it should. I'll prepare a patch for doing this.
Bruno
___
bug-gnulib mailing list
bu
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote on 2005-12-06:
>> >> Shouldn't csharpcomp-script and javacomp-script also invoke
>> >> AC_CONFIG_FILES on the scripts? I need to do that manually now, and
>> >> gnulib-tool didn't tell me about it.
>> >>
>> >> I can't come up with a
Simon Josefsson wrote on 2005-12-06:
> >> Shouldn't csharpcomp-script and javacomp-script also invoke
> >> AC_CONFIG_FILES on the scripts? I need to do that manually now, and
> >> gnulib-tool didn't tell me about it.
> >>
> >> I can't come up with a simple patch -- the AC_CONFIG_FILES statement
>
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> > - automake's support uses only gcj, ignoring the "javac" and "jikes"
>> > commands.
>>
>> Right.
>>
>> > - It completely ignores CLASSPATH issues.
>>
>> Which, automake or javacomp?
>
> I meant, automake.
>
>> I'd like to sup
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> Shouldn't csharpcomp-script and javacomp-script also invoke
>> AC_CONFIG_FILES on the scripts? I need to do that manually now, and
>> gnulib-tool didn't tell me about it.
>>
>> I can't come up with a simple patch -- the AC_CONFI
Simon Josefsson wrote:
> > - automake's support uses only gcj, ignoring the "javac" and "jikes"
> > commands.
>
> Right.
>
> > - It completely ignores CLASSPATH issues.
>
> Which, automake or javacomp?
I meant, automake.
> I'd like to support javac and jikes.
javacomp supports it.
> Does java
Simon Josefsson wrote:
> Shouldn't csharpcomp-script and javacomp-script also invoke
> AC_CONFIG_FILES on the scripts? I need to do that manually now, and
> gnulib-tool didn't tell me about it.
>
> I can't come up with a simple patch -- the AC_CONFIG_FILES statement
> would have to include the dir
Shouldn't csharpcomp-script and javacomp-script also invoke
AC_CONFIG_FILES on the scripts? I need to do that manually now, and
gnulib-tool didn't tell me about it.
I can't come up with a simple patch -- the AC_CONFIG_FILES statement
would have to include the directory somehow. It should probabl
Bruno Haible <[EMAIL PROTECTED]> writes:
>> I'm now using csharpcomp to build the Libidn C# port.
>>
>> How does javacomp relate to the automake Java support?
>
> - automake's support uses only gcj, ignoring the "javac" and "jikes"
> commands.
Right.
> - It completely ignores CLASSPATH issues.
Simon Josefsson wrote:
> > * modules/csharpcomp: Depend on it.
> > * modules/javacomp: Depend on it.
>
> These two patches were forgotten, apparently.
Oops, fixed. Sorry, I'm constantly in a hurry these days.
> I'm now using csharpcomp to build the Libidn C# port.
>
> How does javacomp re
Bruno Haible <[EMAIL PROTECTED]> 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
Bruno Haible <[EMAIL PROTECTED]> 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
Simon Josefsson wrote:
> After including the csharpcomp module in libidn, I realized I don't
> need any of the C code in that module. I just need csharpcomp.sh.in,
> csharp.m4 and csharpcomp.m4.
>
> How about installing the following csharpcomp-script module for those
> files, and patching the csh
Simon Josefsson <[EMAIL PROTECTED]> writes:
> How about changing the License of the csharpcomp-script module to
> "helper-GPL", and make "helper-GPL" LGPL-compatible, as far as
> gnulib-tool is concerned?
To clarify: gnulib-tool should NOT alter the GPL license template in
csharpcomp.sh.in here.
After including the csharpcomp module in libidn, I realized I don't
need any of the C code in that module. I just need csharpcomp.sh.in,
csharp.m4 and csharpcomp.m4.
How about installing the following csharpcomp-script module for those
files, and patching the csharpcomp module to depend on the fo
19 matches
Mail list logo
