Hi.
My libidn.texi file uses @include and @verbatiminclude to get files
stored in other directories (examples, and auto-generated *.texi
snippets found in builddir), I need to pass some -I flags to makeinfo:
AM_MAKEINFOFLAGS = -I $(top_builddir)/doc -I $(top_srcdir)/examples
AM_MAKEINFOHTMLFLAGS = $(AM_MAKEINFOFLAGS) \
--no-split --number-sections --css-include=texinfo.css
It seems texi2dvi also needs this parameter, otherwise it fails to find
the @include-files. Thus I have added this:
TEXI2DVI = texi2dvi $(AM_MAKEINFOFLAGS)
However, turning on automake warnings results in:
doc/Makefile.am:44: user variable `TEXI2DVI' defined here...
/usr/local/share/automake-1.10/am/texinfos.am: ... overrides Automake variable
`TEXI2DVI' defined here
I understand TEXI2DVI is a user variable, but I cannot find any way to
pass the -I's to texi2dvi without doing this. There is a generated rule
like:
.texi.dvi:
TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I
$(srcdir)' \
$(TEXI2DVI) $<
But given that the appropriate -I's are already present in
AM_MAKEINFOFLAGS for me, it isn't sufficient.
Thus, my request is for automake to offer a way to add parameters to
TEXI2DVI and consequently to TEXI2PDF as well [1].
Alternatively, texi2dvi in texinfo could be extended to parse -I's from
the MAKEINFO variable.
Thoughts?
Thanks,
/Simon
[1] TEXI2PDF = $(TEXI2DVI) --pdf --batch
