Re: Target to make PS/PDF documentation?

[Ethan M. <merritt@u.washington.edu>]

On Thursday 04 September 2008 12:01:49 Hans-Bernhard Bröker wrote:
> Ethan A Merritt wrote:
> > As Phillip pointed out, however, not all of the subdirectory
> > targets are recognized from the top level directory.  
> 
> Ultimately the reason is that docs/Makefile.in is not made from a 
> docs/Makefile.am, 

I'm just trying to understand the mechanism.
"make pdf" does work from the top level directory,
but "make pdffigures" does not.  Why?
Some piece of the automake/autoconf process adds the necessary
dummy targets for pdf (and pdf-recursive) in all subdirectories.
But what triggers this?  
Is there some keyword I can add somewhere that will do the same for pdffigures?


	Ethan



> and that gnuplot.info is not our primary documentation  
> source file.  If it were, it would only take a single line in 
> docs/Makefile.am:
> 
>     info_TEXINFOS = gnuplot.info
> 
> and automake would automatically set up rules build the documentation in 
> various formats. The only downside, if any, would be that texinfo's  
> "makeinfo" program would become a build prerequisite, since automake 
> insists on building and installing at least the info version in such a case.
> 
> Oh, and FWIW, the options for building the other help document formats 
> _are_ pointed at: right there in README it says:
> 
> <quote>The new gnuplot user should begin by reading the general information
> available by typing `help` after running gnuplot. Then read about the
> `plot` command (type `help plot`).  The manual for gnuplot (which is a
> nicely formatted version of the on-line help information) can be
> printed either with TeX, troff or nroff.  Look at the docs/Makefile
> for the appropriate option.</quote>
> 
> And once you do look into docs/Makefile (or Makefile.in, if you haven't 
> configured yet), it does mention ps, pdf and friends quite clearly.
> 



-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742