automake-ng
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Automake-NG] [PATCH 02/26] [ng] texi: tweak rules for HTML generati


From: Stefano Lattarini
Subject: Re: [Automake-NG] [PATCH 02/26] [ng] texi: tweak rules for HTML generation to spawn only one shell
Date: Sun, 17 Jun 2012 09:41:25 +0200

On 06/17/2012 08:37 AM, Akim Demaille wrote:
> 
> Le 16 juin 2012 à 23:29, Stefano Lattarini a écrit :
> 
>> %.html: %%SOURCE_SUFFIX%
>> -    %SILENT%$(am__ensure_target_dir_exists)
>> +    %AM_V_MAKEINFO%$(am__ensure_target_dir_exists) \
>> ## When --split (the default) is used, makeinfo will output a
>> ## directory.  However it will not update the time stamp of a
>> ## previously existing directory, and when the names of the nodes
>> ## in the manual change, it may leave unused pages.  Our fix
>> ## is to build under a temporary name, and replace the target on
>> ## success.
>> -    %AM_V_MAKEINFO%rm -rf $(@:.html=.htp)
>> -    %SILENT%if $(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) \
>> -                               %MAKEINFOFLAGS% -o $(@:.html=.htp) $<; \
>> +      && { test ! -d $(@:.html=.htp) || rm -rf $(@:.html=.htp); } \
>> +      || exit 1; \
>> +    if $(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) \
>> +                       %MAKEINFOFLAGS% -o $(@:.html=.htp) $<; \
> 
> Why such an extension?
>
It was already in the pre-existing code.  And about the reason it was there,
I guess it was to cater to systems with 8+3 filenames (e.g., DJGPP on DOS),
where one can't have file names with "two or more extensions" (like
'config.h.in' or, in this case, foo.html.tmp).

> address@hidden looks more readable.
>
Or ever 'address@hidden', for consistency with other rules.  But I guess such 
changes
are better done in a later refactoring, to rationalize the names/location of
temporary files.  WDYS?

>>      then \
>>        rm -rf $@; \
>> ## Work around a bug in Texinfo 4.1 (-o foo.html outputs files in foo/
>> -- 
>> 1.7.9.5
>>
>>
> 

Regards,
  Stefano



reply via email to

[Prev in Thread] Current Thread [Next in Thread]