Re: Separate csharpcomp.sh, and a license problem

[Simon Josefsson]

Bruno Haible <address@hidden> 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 simple patch -- the AC_CONFIG_FILES statement
>> >> would have to include the directory somehow.
>> >
>> > You can probably assume that the .sh.in file is in the build-aux dir,
>> > i.e. in $top_srcdir/$ac_aux_dir, and that the .sh file will be put into
>> > the $top_builddir. Like for libtool for example. This should
>> > simplify things.
>> 
>> This doesn't hold for csharpcomp.sh.in, does it?  It is in lib/.
>
> I'm moving it to build-aux.

Seems fine.

>> >> Should we add another line in the modules-file, i.e.:
>> >>
>> >> Config-files:
>> >> lib/csharpcomp.sh
>> >
>> > I don't think this is needed.
>> 
>> Generating the AC_CONFIG_FILES statements like a good thing.  How
>> could that be achieved without a Config-files: statement?
>
> A line in the 'configure.ac:' section is sufficient:
>   AC_CONFIG_FILES([csharpcomp.sh:build-aux/csharpcomp.sh.in])

How would build-aux/ be substituted into $auxdir?  Should gnulib-tool
substitute 'build-aux/' in configure.ac:-statements to $auxdir?  I'm
not sure.

Thanks!