- Timestamp:
- Mar 24, 2023 9:21:19 AM (21 months ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/Makefile.kmk
r99167 r99168 27 27 28 28 # 29 # This slightly messy makefile transforms the DocBook XML source for the 30 # user manual into presentation output. We support two targets: 29 # This makefile produces our user manual (among a few other things) in 30 # 3 formats: qHelp, pdf, and html (chunked and single page). User manual 31 # files are kept in dita format. VBoxManage commands are documented using docbook 32 # refentry elements and integrated into VBoxManage binary after converting those 33 # to .cpp and .h files (not here). Additionally, we add these refentry's into the 34 # user manual as a chapter after converting them into dita files. Both the user manual 35 # and converted VBoxManage commands files are referenced with a single ditamap. 36 # This ditamap is then transformed into html, htmlhelp (for qHelp), and pdf. 31 37 # 32 # -- UserManual.pdf, generated by LaTex 33 # 34 # 35 # Both files end up in PATH_STAGE_BIN. 36 # 37 # Both targets indirectly depend on the XML files in this directory; 38 # "indirectly" because we first copy them to PATH_TARGET and hack them 39 # up a bit for variable substitution and such (see below). 40 # The toolchains are roughly like this: 41 # 42 # -- PDF file via Apache FOP: pre-process the XML files in PATH_TARGET, 43 # then create a .FO file (another XML format for "formatted objects") 44 # via xsltproc, then feed the .FO file to Apache FOP to create the PDF. 45 # 46 # -- PDF file via LaTeX: pre-process the XML files in PATH_TARGET, then 47 # run our custom "dblatex" perl script on UserManual.xml, which parses 48 # the XML (using the Perl SAX parsers) and dumps a matching LaTeX file 49 # to UserManual.tex. This is then regularly processed by pdflatex to 50 # generate PDF. 51 # 52 # 38 53 39 54 40 SUB_DEPTH = ../..
Note:
See TracChangeset
for help on using the changeset viewer.