On a recent MacTeX installation, this yields ``/Library/TeX/texbin\pdflatex/ Mac OS X: Set PDFLATEX_COMPILER to the result of the shell command which pdflatex''. ![]() Windows: Set the CMake variable ``MIKTEX_BINARY_PATH’’ to the directory containing the MikTeX binaries, e.g., ``C:/Program Files/MiKTeX 2.9/miktex/bin/圆4’‘.In particular, if PDFLATEX_COMPILER is not found, fix it as follows: After installing LaTeX and running the CMake configuration stage with the option BUILD_DOCUMENTATION enabled, check for errors and for missing binary paths. So look out for error messages when running the documentation generation for the first time, and use the distribution’s package manager to install the missing packages as needed. Note that - unless you install a “full” distribution - LaTeX packages might be missing and would need to be installed as needed. Linux: The system-provided LaTeX (installed, e.g., through ``sudo apt install texlive-full’’ ``sudo apt install texlive’’ on Ubuntu).We recommend the following LaTeX distributions: LaTeX: Both the Doxygen documentation and the PDF generation of Sphinx require a LaTeX system to be installed. Note that the XML output generation needed for subsequent build stages is quite buggy in older Doxygen releases, it might therefore be advisable to upgrade to a recent Doxygen release or to build from source (especially on Linux, where the version provided by the package manager could be rather dated). On Linux, installing via the distribution-specific package manager (e.g., ``sudo apt install doxygen’‘. In order to create the user and API documentation, the following software tools must be installed:ĭoxygen: On Windows and Mac OS X, we recommend downloading binary packages from the Doxygen download page and installing them. ![]() ![]() The VISR documentation is mainly written as ReStructured text documents (using `Sphinx `_ to create web pages and PDF documents), whereas the code documentation pulled into these documents is generated through Doxygen.
0 Comments
Leave a Reply. |