1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
|
<!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.12"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<title>Doxygen: Getting started</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="navtreedata.js"></script>
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
$(document).ready(initResizable);
</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 id="projectalign" style="padding-left: 0.5em;">
<div id="projectname">Doxygen
</div>
</td>
</tr>
</tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.12 -->
</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('starting.html','');});
</script>
<div id="doc-content">
<div class="header">
<div class="headertitle">
<div class="title">Getting started </div> </div>
</div><!--header-->
<div class="contents">
<div class="toc"><h3>Table of Contents</h3>
<ul><li class="level1"><a href="#step0">Step 0: Check if doxygen supports your programming language</a></li>
<li class="level1"><a href="#step1">Step 1: Creating a configuration file</a></li>
<li class="level1"><a href="#step2">Step 2: Running doxygen</a><ul><li class="level2"><a href="#html_out">HTML output</a></li>
<li class="level2"><a href="#latex_out">LaTeX output</a></li>
<li class="level2"><a href="#rtf_out">RTF output</a></li>
<li class="level2"><a href="#xml_out">XML output</a></li>
<li class="level2"><a href="#man_out">Man page output</a></li>
<li class="level2"><a href="#docbook_out">DocBook output</a></li>
</ul>
</li>
<li class="level1"><a href="#step3">Step 3: Documenting the sources</a></li>
</ul>
</div>
<div class="textblock"><p>The executable <code>doxygen</code> is the main program that parses the sources and generates the documentation. See section <a class="el" href="doxygen_usage.html">Doxygen usage</a> for more detailed usage information.</p>
<p>Optionally, the executable <code>doxywizard</code> can be used, which is a <a class="el" href="doxywizard_usage.html">graphical front-end</a> for editing the configuration file that is used by doxygen and for running doxygen in a graphical environment. For Mac OS X doxywizard will be started by clicking on the doxygen application icon.</p>
<p>The following figure shows the relation between the tools and the flow of information between them (it looks complex but that's only because it tries to be complete):</p>
<div class="image">
<img src="infoflow.png" alt="infoflow.png"/>
<div class="caption">
Doxygen information flow</div></div>
<h1><a class="anchor" id="step0"></a>
Step 0: Check if doxygen supports your programming language</h1>
<p>First, assure that your programming language has a reasonable chance of being recognized by doxygen. These languages are supported by default: C, C++, C#, Objective-C, IDL, Java, VHDL, PHP, Python, Tcl, Fortran, and D. It is possible to configure certain file type extensions to use certain parsers: see the <a class="el" href="config.html#cfg_extension_mapping">Configuration/ExtensionMappings</a> for details. Also, completely different languages can be supported by using preprocessor programs: see the <a href="http://www.doxygen.org/helpers.html">Helpers page</a> for details.</p>
<h1><a class="anchor" id="step1"></a>
Step 1: Creating a configuration file</h1>
<p>Doxygen uses a configuration file to determine all of its settings. Each project should get its own configuration file. A project can consist of a single source file, but can also be an entire source tree that is recursively scanned.</p>
<p>To simplify the creation of a configuration file, doxygen can create a template configuration file for you. To do this call <code>doxygen</code> from the command line with the <code>-g</code> option: </p><pre class="fragment">doxygen -g <config-file>
</pre><p>where <config-file> is the name of the configuration file. If you omit the file name, a file named <code>Doxyfile</code> will be created. If a file with the name <config-file> already exists, doxygen will rename it to <config-file>.bak before generating the configuration template. If you use <code>-</code> (i.e. the minus sign) as the file name then doxygen will try to read the configuration file from standard input (<code>stdin</code>), which can be useful for scripting.</p>
<p>The configuration file has a format that is similar to that of a (simple) Makefile. It consists of a number of assignments (tags) of the form:</p>
<p><code>TAGNAME = VALUE</code> or <br />
<code>TAGNAME = VALUE1 VALUE2 ... </code><br />
</p>
<p>You can probably leave the values of most tags in a generated template configuration file to their default value. See section <a class="el" href="config.html">Configuration</a> for more details about the configuration file.</p>
<p>If you do not wish to edit the config file with a text editor, you should have a look at <a class="el" href="doxywizard_usage.html">doxywizard</a>, which is a GUI front-end that can create, read and write doxygen configuration files, and allows setting configuration options by entering them via dialogs.</p>
<p>For a small project consisting of a few C and/or C++ source and header files, you can leave <a class="el" href="config.html#cfg_input">INPUT</a> tag empty and doxygen will search for sources in the current directory.</p>
<p>If you have a larger project consisting of a source directory or tree you should assign the root directory or directories to the <a class="el" href="config.html#cfg_input">INPUT</a> tag, and add one or more file patterns to the <a class="el" href="config.html#cfg_file_patterns">FILE_PATTERNS</a> tag (for instance <code>*.cpp *.h</code>). Only files that match one of the patterns will be parsed (if the patterns are omitted a list of typical patterns is used for the types of files doxygen supports). For recursive parsing of a source tree you must set the <a class="el" href="config.html#cfg_recursive">RECURSIVE</a> tag to <code>YES</code>. To further fine-tune the list of files that is parsed the <a class="el" href="config.html#cfg_exclude">EXCLUDE</a> and <a class="el" href="config.html#cfg_exclude_patterns">EXCLUDE_PATTERNS</a> tags can be used. To omit all <code>test</code> directories from a source tree for instance, one could use:</p>
<pre class="fragment">EXCLUDE_PATTERNS = */test/*
</pre><p>Doxygen looks at the file's extension to determine how to parse a file, using the following table:</p>
<table class="doxtable">
<tr>
<th align="right">Extension </th><th>Language </th></tr>
<tr>
<td align="right">.idl </td><td>IDL </td></tr>
<tr>
<td align="right">.ddl </td><td>IDL </td></tr>
<tr>
<td align="right">.odl </td><td>IDL </td></tr>
<tr>
<td align="right">.java </td><td>Java </td></tr>
<tr>
<td align="right">.cs </td><td>C# </td></tr>
<tr>
<td align="right">.d </td><td>D </td></tr>
<tr>
<td align="right">.php </td><td>PHP </td></tr>
<tr>
<td align="right">.php4 </td><td>PHP </td></tr>
<tr>
<td align="right">.php5 </td><td>PHP </td></tr>
<tr>
<td align="right">.inc </td><td>PHP </td></tr>
<tr>
<td align="right">.phtml </td><td>PHP </td></tr>
<tr>
<td align="right">.m </td><td>Objective-C </td></tr>
<tr>
<td align="right">.M </td><td>Objective-C </td></tr>
<tr>
<td align="right">.mm </td><td>Objective-C </td></tr>
<tr>
<td align="right">.py </td><td>Python </td></tr>
<tr>
<td align="right">.f </td><td>Fortran </td></tr>
<tr>
<td align="right">.for </td><td>Fortran </td></tr>
<tr>
<td align="right">.f90 </td><td>Fortran </td></tr>
<tr>
<td align="right">.f95 </td><td>Fortran </td></tr>
<tr>
<td align="right">.f03 </td><td>Fortran </td></tr>
<tr>
<td align="right">.f08 </td><td>Fortran </td></tr>
<tr>
<td align="right">.vhd </td><td>VHDL </td></tr>
<tr>
<td align="right">.vhdl </td><td>VHDL </td></tr>
<tr>
<td align="right">.tcl </td><td>TCL </td></tr>
<tr>
<td align="right">.ucf </td><td>VHDL </td></tr>
<tr>
<td align="right">.qsf </td><td>VHDL </td></tr>
<tr>
<td align="right">.md </td><td>Markdown </td></tr>
<tr>
<td align="right">.markdown </td><td>Markdown </td></tr>
</table>
<p>Any other extension is parsed as if it is a C/C++ file.</p>
<p><a class="anchor" id="extract_all"></a>If you start using doxygen for an existing project (thus without any documentation that doxygen is aware of), you can still get an idea of what the structure is and how the documented result would look like. To do so, you must set the <a class="el" href="config.html#cfg_extract_all">EXTRACT_ALL</a> tag in the configuration file to <code>YES</code>. Then, doxygen will pretend everything in your sources is documented. Please note that as a consequence warnings about undocumented members will not be generated as long as <a class="el" href="config.html#cfg_extract_all">EXTRACT_ALL</a> is set to <code>YES</code>.</p>
<p>To analyze an existing piece of software it is useful to cross-reference a (documented) entity with its definition in the source files. Doxygen will generate such cross-references if you set the <a class="el" href="config.html#cfg_source_browser">SOURCE_BROWSER</a> tag to <code>YES</code>. It can also include the sources directly into the documentation by setting <a class="el" href="config.html#cfg_inline_sources">INLINE_SOURCES</a> to <code>YES</code> (this can be handy for code reviews for instance).</p>
<h1><a class="anchor" id="step2"></a>
Step 2: Running doxygen</h1>
<p>To generate the documentation you can now enter: </p><pre class="fragment">doxygen <config-file>
</pre><p>Depending on your settings doxygen will create <code>html</code>, <code>rtf</code>, <code>latex</code>, <code>xml</code>, <code>man</code>, and/or docbook directories inside the output directory. As the names suggest these directories contain the generated documentation in HTML, RTF, <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/>, XML, Unix-Man page, and DocBook format.</p>
<p>The default output directory is the directory in which <code>doxygen</code> is started. The root directory to which the output is written can be changed using the <a class="el" href="config.html#cfg_output_directory">OUTPUT_DIRECTORY</a>. The format specific directory within the output directory can be selected using the <a class="el" href="config.html#cfg_html_output">HTML_OUTPUT</a>, <a class="el" href="config.html#cfg_rtf_output">RTF_OUTPUT</a>, <a class="el" href="config.html#cfg_latex_output">LATEX_OUTPUT</a>, <a class="el" href="config.html#cfg_xml_output">XML_OUTPUT</a>, <a class="el" href="config.html#cfg_man_output">MAN_OUTPUT</a>, and <a class="el" href="config.html#cfg_docbook_output">DOCBOOK_OUTPUT</a>. tags of the configuration file. If the output directory does not exist, <code>doxygen</code> will try to create it for you (but it will <em>not</em> try to create a whole path recursively, like <code>mkdir -p</code> does).</p>
<h2><a class="anchor" id="html_out"></a>
HTML output</h2>
<p><a name="abrowser"></a> The generated HTML documentation can be viewed by pointing a HTML browser to the <code>index.html</code> file in the <code>html</code> directory. For the best results a browser that supports cascading style sheets (CSS) should be used (I'm using Mozilla Firefox, Google Chrome, Safari, and sometimes IE8, IE9, and Opera to test the generated output).</p>
<p>Some of the features the HTML section (such as <a class="el" href="config.html#cfg_generate_treeview">GENERATE_TREEVIEW</a> or the search engine) require a browser that supports Dynamic HTML and Javascript enabled.</p>
<h2><a class="anchor" id="latex_out"></a>
LaTeX output</h2>
<p><a name="aLaTeX"></a> The generated <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/> documentation must first be compiled by a <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/> compiler (I use a recent teTeX distribution for Linux and MacOSX and MikTex for Windows). To simplify the process of compiling the generated documentation, <code>doxygen</code> writes a <code>Makefile</code> into the <code>latex</code> directory (on the Windows platform also a <code>make.bat</code> batch file is generated).</p>
<p>The contents and targets in the <code>Makefile</code> depend on the setting of <a class="el" href="config.html#cfg_use_pdflatex">USE_PDFLATEX</a>. If it is disabled (set to <code>NO</code>), then typing <code>make</code> in the <code>latex</code> directory a <code>dvi</code> file called <code>refman.dvi</code> will be generated. This file can then be viewed using <code>xdvi</code> or converted into a PostScript file <code>refman.ps</code> by typing <code>make ps</code> (this requires <code>dvips</code>).</p>
<p>To put 2 pages on one physical page use <code>make ps_2on1</code> instead. The resulting PostScript file can be send to a PostScript printer. If you do not have a PostScript printer, you can try to use ghostscript to convert PostScript into something your printer understands.</p>
<p>Conversion to PDF is also possible if you have installed the ghostscript interpreter; just type <code>make pdf</code> (or <code>make pdf_2on1</code>).</p>
<p>To get the best results for PDF output you should set the <a class="el" href="config.html#cfg_pdf_hyperlinks">PDF_HYPERLINKS</a> and <a class="el" href="config.html#cfg_use_pdflatex">USE_PDFLATEX</a> tags to <code>YES</code>. In this case the <code>Makefile</code> will only contain a target to build <code>refman.pdf</code> directly.</p>
<h2><a class="anchor" id="rtf_out"></a>
RTF output</h2>
<p><a name="aRTF"></a> Doxygen combines the RTF output to a single file called refman.rtf. This file is optimized for importing into the Microsoft Word. Certain information is encoded using so called fields. To show the actual value you need to select all (Edit - select all) and then toggle fields (right click and select the option from the drop down menu).</p>
<h2><a class="anchor" id="xml_out"></a>
XML output</h2>
<p><a name="aXML"></a> The XML output consists of a structured "dump" of the information gathered by doxygen. Each compound (class/namespace/file/...) has its own XML file and there is also an index file called <code>index.xml</code>.</p>
<p>A file called <code>combine.xslt</code> XSLT script is also generated and can be used to combine all XML files into a single file.</p>
<p>Doxygen also generates two XML schema files <code>index.xsd</code> (for the index file) and <code>compound.xsd</code> (for the compound files). This schema file describes the possible elements, their attributes and how they are structured, i.e. it the describes the grammar of the XML files and can be used for validation or to steer XSLT scripts.</p>
<p>In the <code>addon/doxmlparser</code> directory you can find a parser library for reading the XML output produced by doxygen in an incremental way (see <code>addon/doxmlparser/include/doxmlintf.h</code> for the interface of the library)</p>
<h2><a class="anchor" id="man_out"></a>
Man page output</h2>
<p><a name="aman"></a> The generated man pages can be viewed using the <code>man</code> program. You do need to make sure the man directory is in the man path (see the <code>MANPATH</code> environment variable). Note that there are some limitations to the capabilities of the man page format, so some information (like class diagrams, cross references and formulas) will be lost.</p>
<h2><a class="anchor" id="docbook_out"></a>
DocBook output</h2>
<p><a name="adocbook"></a> Doxygen can also generate output in the <a href="http://www.docbook.org/">DocBook</a> format. How to process the DocBook output is beyond the scope of this manual.</p>
<h1><a class="anchor" id="step3"></a>
Step 3: Documenting the sources</h1>
<p>Although documenting the sources is presented as step 3, in a new project this should of course be step 1. Here I assume you already have some code and you want doxygen to generate a nice document describing the API and maybe the internals and some related design documentation as well.</p>
<p>If the <a class="el" href="config.html#cfg_extract_all">EXTRACT_ALL</a> option is set to <code>NO</code> in the configuration file (the default), then doxygen will only generate documentation for <em>documented</em> entities. So how do you document these? For members, classes and namespaces there are basically two options:</p><ol type="1">
<li><p class="startli">Place a <em>special</em> documentation block in front of the declaration or definition of the member, class or namespace. For file, class and namespace members it is also allowed to place the documentation directly after the member.</p>
<p class="startli">See section <a class="el" href="docblocks.html#specialblock">Special comment blocks</a> to learn more about special documentation blocks.</p>
</li>
<li><p class="startli">Place a special documentation block somewhere else (another file or another location) <em>and</em> put a <em>structural command</em> in the documentation block. A structural command links a documentation block to a certain entity that can be documented (e.g. a member, class, namespace or file).</p>
<p class="startli">See section <a class="el" href="docblocks.html#structuralcommands">Documentation at other places</a> to learn more about structural commands.</p>
</li>
</ol>
<p>The advantage of the first option is that you do not have to repeat the name of the entity.</p>
<p>Files can only be documented using the second option, since there is no way to put a documentation block before a file. Of course, file members (functions, variables, typedefs, defines) do not need an explicit structural command; just putting a special documentation block in front or behind them will work fine.</p>
<p>The text inside a special documentation block is parsed before it is written to the HTML and/or <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/> output files.</p>
<p><a name="aparsing"></a> During parsing the following steps take place:</p><ul>
<li>Markdown formatting is replaced by corresponding HTML or special commands.</li>
<li>The special commands inside the documentation are executed. See section <a class="el" href="commands.html">Special Commands</a> for an overview of all commands.</li>
<li>If a line starts with some whitespace followed by one or more asterisks (<code>*</code>) and then optionally more whitespace, then all whitespace and asterisks are removed.</li>
<li>All resulting blank lines are treated as a paragraph separators. This saves you from placing new-paragraph commands yourself in order to make the generated documentation readable.</li>
<li>Links are created for words corresponding to documented classes (unless the word is preceded by a %; then the word will not be linked and the % sign is removed).</li>
<li>Links to members are created when certain patterns are found in the text. See section <a class="el" href="autolink.html">Automatic link generation</a> for more information on how the automatic link generation works.</li>
<li>HTML tags that are in the documentation are interpreted and converted to <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/> equivalents for the <img class="formulaInl" alt="$\mbox{\LaTeX}$" src="form_0.png"/> output. See section <a class="el" href="htmlcmds.html">HTML Commands</a> for an overview of all supported HTML tags.</li>
</ul>
<p>
Go to the <a href="docblocks.html">next</a> section or return to the
<a href="index.html">index</a>.
</p>
</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.12 </li>
</ul>
</div>
</body>
</html>
|
