> 26. 1. 2018 v 14:58, Vaclav Hapla <[email protected]>: > > > >> 26. 1. 2018 v 14:08, Vaclav Hapla <[email protected] >> <mailto:[email protected]>>: >> >> >> >>> 26. 1. 2018 v 14:03, Patrick Sanan <[email protected] >>> <mailto:[email protected]>>: >>> >>> There is probably a better way but what's worked for me here is to make >>> sure I have pdflatex on my system (sudo apt install texlive, or similar), >>> then "make reconfigure", which seems to set PDFLATEX as required, and then >>> something like >>> >>> cd src/docs/tex/manual >>> make manual.pdf LOC=$PETSC_DIR >>> cd ../../../docs >>> # manual.pdf should be there >> >> Thanks, Patrick. It would be definitely a better way. But I have installed >> PETSc into Linux with texlive installed and pdflatex command in PATH, and >> still the PDFLATEX variable hasn't got set. > > There must be something broken in my system as I also get bunch of > /bin/sh: 2: -map: not found > errors for > make alldoc LOC=${PETSC_DIR} > which means also MAPNAMES is not set. > I started from scratch in different PETSc clone and it's the same. > Interesting.
The variables were not set because sowing was not installed. It didn't come to my mind as sowing is not directly related to the PDF manual processing. Damn. > > Vaclav > >> >> Vaclav >> >>> >>> 2018-01-26 14:00 GMT+01:00 Vaclav Hapla <[email protected] >>> <mailto:[email protected]>>: >>> >>> >>> > 25. 1. 2018 v 9:33, Smith, Barry F. <[email protected] >>> > <mailto:[email protected]>>: >>> > >>> > >>> > src/docs/tex/manual/developers.tex there is also a make file that >>> > generates the PDF. >>> >>> I'm trying to build the manual. Apparently the PDFLATEX variable is not >>> set. So I set it externally and it works - is it supposed to be done this >>> way? Would you mind adding the PDFLATEX variable into >>> ${PETSC_DIR}/lib/petsc/conf/variables? Perhaps with assigned using ?= so >>> that it could be overridden? >>> >>> Vaclav >>> >>> > >>> > Barry >>> > >>> > The document should provide information about the location of its source. >>> > >>> > >>> > >>> >> On Jan 25, 2018, at 2:19 AM, Vaclav Hapla <[email protected] >>> >> <mailto:[email protected]>> wrote: >>> >> >>> >> >>> >> >>> >>> 24. 1. 2018 v 22:55, Scott Kruger <[email protected] >>> >>> <mailto:[email protected]>>: >>> >>> >>> >>> >>> >>> >>> >>> On 1/24/18 6:50 AM, Vaclav Hapla wrote: >>> >>>>> 24. 1. 2018 v 14:45, Vaclav Hapla <[email protected] >>> >>>>> <mailto:[email protected]>>: >>> >>>>> >>> >>>>> How should I specify output files for {{...}} with different outputs, >>> >>>>> please? >>> >>>> Oh I see, {{...}separateoutput} is meant literally. But in that case >>> >>>> typesetting it in italics is confusing. >>> >>> >>> >>> It's clearer in the examples listed below. I couldn't get lstinline >>> >>> to work for this syntax so used $ ... $. If someone knows how to do >>> >>> it, please feel free to fix. >>> >> >>> >> Where are this manual's latex sources? >>> >> >>> >> Vaclav >>> >> >>> >>> >>> >>> Scott >>> >>> >>> >>>> Vaclav >>> >>>>> >>> >>>>> I have consulted the developers manual but it's not clear to me >>> >>>>> still. And the example listings, page 34-45, seem to be broken. >>> >>>>> >>> >>>>> BTW in 7.1.2, I think there should be the space instead of the comma >>> >>>>> in the listing. >>> >>>>> >>> >>>>> Thanks >>> >>>>> >>> >>>>> Vaclav >>> >>> >>> >>> -- >>> >>> Tech-X Corporation [email protected] >>> >>> <mailto:[email protected]> >>> >>> 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 >>> >>> <tel:%28720%29%20974-1841> >>> >>> Boulder, CO 80303 Fax: (303) 448-7756 >>> >>> <tel:%28303%29%20448-7756> >>> >> >>> >
