EVOLUTION-MANAGER
Edit File: doxygen_usage.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/> <meta http-equiv="X-UA-Compatible" content="IE=9"/> <meta name="generator" content="Doxygen 1.8.5"/> <title>Doxygen: Doxygen usage</title> <link href="tabs.css" rel="stylesheet" type="text/css"/> <script type="text/javascript" src="jquery.js"></script> <script type="text/javascript" src="dynsections.js"></script> <link href="navtree.css" rel="stylesheet" type="text/css"/> <script type="text/javascript" src="resize.js"></script> <script type="text/javascript" src="navtree.js"></script> <script type="text/javascript"> $(document).ready(initResizable); $(window).load(resizeHeight); </script> <link href="doxygen_manual.css" rel="stylesheet" type="text/css" /> </head> <body> <div id="top"><!-- do not remove this div, it is closed by doxygen! --> <div id="titlearea"> <table cellspacing="0" cellpadding="0"> <tbody> <tr style="height: 56px;"> <td style="padding-left: 0.5em;"> <div id="projectname">Doxygen </div> </td> </tr> </tbody> </table> </div> <!-- end header part --> <!-- Generated by Doxygen 1.8.5 --> </div><!-- top --> <div id="side-nav" class="ui-resizable side-nav-resizable"> <div id="nav-tree"> <div id="nav-tree-contents"> <div id="nav-sync" class="sync"></div> </div> </div> <div id="splitbar" style="-moz-user-select:none;" class="ui-resizable-handle"> </div> </div> <script type="text/javascript"> $(document).ready(function(){initNavTree('doxygen_usage.html','');}); </script> <div id="doc-content"> <div class="header"> <div class="headertitle"> <div class="title">Doxygen usage </div> </div> </div><!--header--> <div class="contents"> <div class="textblock"><p>Doxygen is a command line based utility. Calling <code>doxygen</code> with the <code>–help</code> option at the command line will give you a brief description of the usage of the program.</p> <p>All options consist of a leading character <code>-</code>, followed by one character and one or more arguments depending on the option.</p> <p>To generate a manual for your project you typically need to follow these steps: </p> <ol> <li> You document your source code with special documentation blocks (see section <a class="el" href="docblocks.html#specialblock">Special comment blocks</a>). </li> <li> You generate a configuration file (see section <a class="el" href="config.html">Configuration</a>) by calling doxygen with the <code>-g</code> option: <pre class="fragment">doxygen -g <config_file> </pre> </li> <li> You edit the configuration file so it matches your project. In the configuration file you can specify the input files and a lot of optional information. </li> <li> You let doxygen generate the documentation, based on the settings in the configuration file: <pre class="fragment">doxygen <config_file> </pre> </li> </ol> <p>If you have a configuration file generated with an older version of doxygen, you can upgrade it to the current version by running doxygen with the -u option. </p> <pre class="fragment">doxygen -u <config_file> </pre><p> All configuration settings in the original configuration file will be copied to the new configuration file. Any new options will have their default value. Note that comments that you may have added in the original configuration file will be lost.</p> <h1><a class="anchor" id="doxygen_finetune"></a> Fine-tuning the output</h1> <p>If you want to fine-tune the way the output looks, doxygen allows you generate default style sheet, header, and footer files that you can edit afterwards: </p> <ul> <li> <p class="startli">For HTML output, you can generate the default header file (see <a class="el" href="config.html#cfg_html_header">HTML_HEADER</a>), the default footer (see <a class="el" href="config.html#cfg_html_footer">HTML_FOOTER</a>), and the default style sheet (see <a class="el" href="config.html#cfg_html_stylesheet">HTML_STYLESHEET</a>), using the following command: </p> <pre class="fragment">doxygen -w html header.html footer.html stylesheet.css <config_file> </pre><p> The <code>config_file</code> is optional. When omitted doxygen will search for a file named <code>Doxyfile</code> and process that. When this is also not found it will used the default settings.</p> <p class="endli"></p> </li> <li> For <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/> output, you can generate the first and last part of <code>refman.tex</code> (see <a class="el" href="config.html#cfg_latex_header">LATEX_HEADER</a> and <a class="el" href="config.html#cfg_latex_footer">LATEX_FOOTER</a>) and the style sheet included by that header (normally <code>doxygen.sty</code>), using the following command: <pre class="fragment">doxygen -w latex header.tex footer.tex doxygen.sty <config_file> </pre> If you need non-default options (for instance to use extra <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/> packages) you need to make a config file with those options set correctly and then specify that config file after the generated files (make a backup of the configuration file first so you don't loose it in case you forget to specify one of the output files). </li> <li> For RTF output, you can generate the default style sheet file (see <a class="el" href="config.html#cfg_rtf_stylesheet_file">RTF_STYLESHEET_FILE</a>) using: <pre class="fragment">doxygen -w rtf rtfstyle.cfg </pre> </li> </ul> <dl class="section warning"><dt>Warning</dt><dd>When using a custom header you are responsible for the proper inclusion of any scripts and style sheets that doxygen needs, which is dependent on the configuration options and may changes when upgrading to a new doxygen release.</dd></dl> <dl class="section note"><dt>Note</dt><dd><ul> <li> If you do not want documentation for each item inside the configuration file then you can use the optional <code>-s</code> option. This can use be used in combination with the <code>-u</code> option, to add or strip the documentation from an existing configuration file. Please use the <code>-s</code> option if you send me a configuration file as part of a bug report! </li> <li> To make doxygen read/write to standard input/output instead of from/to a file, use <code>-</code> for the file name. </li> </ul> </dd></dl> Go to the <a href="doxywizard_usage.html">next</a> section or return to the <a href="index.html">index</a>. </div></div><!-- contents --> </div><!-- doc-content --> <!-- start footer part --> <div id="nav-path" class="navpath"><!-- id is needed for treeview function! --> <ul> <li class="footer">Generated by <a href="http://www.doxygen.org/index.html"> <img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.5 </li> </ul> </div> </body> </html>