Hello Ed,
* Ed Hartnett wrote on Tue, Aug 29, 2006 at 01:20:36AM CEST:
# Get lists of the corresponding ps, info, and pdf files.
ps_docs = ${info_TEXINFOS:.texi=.ps}
pdf_docs = ${info_TEXINFOS:.texi=.pdf}
info_docs= ${info_TEXINFOS:.texi=.info}
txt_docs= ${info_TEXINFOS:.texi=.txt}
#
Hello,
On Mon, Aug 28, 2006 at 06:04:13PM -0700, Tyler MacDonald wrote:
Ed Hartnett [EMAIL PROTECTED] wrote:
It sounds like the best plan would be to add a flag to configure
that indicates you want to build docs, like --with-build-docs using
AC_ARG_WITH. [...]
a quick comment from a
Ralf Wildenhues [EMAIL PROTECTED] writes:
Hello Ed,
Howdy Ralf!
With PS this is reasonable: the .dvi file is not in the distribution,
so the make rules try to update that. (Portable make syntax is not able
to express this kind of intermediate dependency.) Solution is to put
netcdf.dvi
Stepan Kasal [EMAIL PROTECTED] writes:
Hello,
On Mon, Aug 28, 2006 at 06:04:13PM -0700, Tyler MacDonald wrote:
Ed Hartnett [EMAIL PROTECTED] wrote:
It sounds like the best plan would be to add a flag to configure
that indicates you want to build docs, like --with-build-docs using
Howdy all!
I have some documentation which accompanies my library. I would like
to install the documentation on the user machine, without building it
on the user machine.
What I want is to build the documentation on the developer's machine,
include it in the distribution, and then install it.
Ed Hartnett [EMAIL PROTECTED] wrote:
What I want is to build the documentation on the developer's machine,
include it in the distribution, and then install it.
The documents are all texinfo documents, and we cannot require that
every user machine have texinfo and tex installed.
It
