openbmc-docs/Makefile, branch master

userguide: update path to code-update

2018-11-07T01:58:51+00:00

This was moved in c4c7f4055387 ("Moved host code update to own doc") but no one updated the makefile. Change-Id: I2b0b3aad6d2436c9cb207a4faeff7468e54a5b2a Signed-off-by: Joel Stanley

Makefile: Document how to build

2018-11-07T01:58:51+00:00

Change-Id: Ief393626f9ca5a838eba574e6b70587405118d4e Signed-off-by: Joel Stanley

userguide: run tex twice

2016-05-26T03:15:14+00:00

.. to generate proper cross-references. Signed-off-by: Jeremy Kerr

userguide: don't run tex in interactive mode

2016-05-26T03:14:14+00:00

... as it doesn't behave well with CI builds. Signed-off-by: Jeremy Kerr

userguide: Don't use pandoc for final tex output

2016-05-26T03:12:55+00:00

When using pandoc to create the main .tex document, we lose all styles and formatting information in the main userguide doc. This change reverts commit bba5b1817e89bd63766e2bb91d406130f027fcaf, and adds the \tighlist macro that was required by that change. Signed-off-by: Jeremy Kerr

Makefile: Remove xelatex build log on clean

2016-05-09T06:03:54+00:00

Previously the log files from xelatex were being left behind. Also, as xelatex now builds the generated userguide.tex, the arguments to rm can be matched by the userguide.* wildcard along with *.tex to remove the remaining pandoc output. Signed-off-by: Andrew Jeffery

userguide: Generate userguide.tex to include \tightlist macro

2016-05-09T05:40:34+00:00

Allow xelatex to build userguide.pdf without errors. pandoc injects \tightlist macros into its output files which cause xelatex to choke. By processing the hand-rolled userguide.tex with pandoc the definition is injected and xelatex can build the PDF. Signed-off-by: Andrew Jeffery

Add infrastructure for User Guide

2016-05-05T07:08:23+00:00

This change adds a little infrastructure for creating an OpenBMC User's Guide, from the user-related documents in markdown. Signed-off-by: Jeremy Kerr