DoxyPress
1.7.0
|
This section covers frequently asked questions about DoxyPress.
Use the \mainpage command inside a comment block as follows:
/*! \mainpage My Index Page * * \section intro_sec Introduction * * This is the introduction for my application of project. * * \section install_sec Installation * * \subsection step1 Step 1: Opening the box * * etc... */
Check the following:
YES
in the project file.YES
to make them appear in the documentation.Is there a macro in your class which does not end with a semicolon? If so then you have to instruct our preprocessor to remove it. This requires the following settings in your project file:
ENABLE-PREPROCESSING = YES MACRO-EXPANSION = YES EXPAND-ONLY-PREDEFINED = YES PREDEFINED-MACROS = MY_MACRO()=
In order for global functions, variables, enums, typedefs, and defines to be documented you should document the file in which these commands are located using a comment block containing a cmdfile command.
Alternatively, you can put all members in a group (or module) using the cmdingroup command and then document the group using a comment block containing the cmddefgroup command.
For member functions or functions which are part of a namespace you should document either the class or namespace.
Add a comment block with a cmdcond command at the start and a second comment block with a cmdendcond command at the end.
The DoxyPress preprocessor can also be used as follows:
#ifndef DOXYPRESS_SHOULD_SKIP_THIS /* code that must be skipped by DoxyPress */ #endif
You will also need to add the following to the predefined-macros tag in the project file.
PREDEFINED = DOXYPRESS_SHOULD_SKIP_THIS
Normally the strip-from-inc-path is used to strip off part of a path. You can also document your class similar to the following:
/*! \class MyClassName include.h path/include.h * * Docs for MyClassName */
If you want DoxyPress to show the include file with quotes instead of angle brackets, document your class as follows:
/*! \class MyClassName include.h "path/include.h" * * Docs for MyClassName */
If you want to refer from one compressed HTML file called a.chm
to another compressed HTML file called b.chm
, the link in a.chm
must have the following format:
<a href="b.chm::/file.html">
The only works if both compressed HTML files are in the same directory. As a result you must rename the generated index.chm
files for all projects into something unique and put all .chm
files in one directory.
With project "A" referring to project "B" using tag file b.tag
, rename the index.chm
for project "A" to a.chm
and the index.chm
for project "B" to b.chm
. In the project file for project "A" set the following:
TAGFILES = b.tag=b.chm::
Verify you have included the stylesheet doxypress.css
in your custom HTML header file.
<LINK HREF="doxypress.css" REL="stylesheet" TYPE="text/css">
Add an exclude pattern in your project file like the following:
EXCLUDE_PATTERNS = */test/*
Place a % in front of the class name. As an example: %MyClass. DoxyPress will remove the "%" and the word will be unlinked.
You can edit the texmf.cfg file to increase the default values of the various buffers and then run "texconfig init".
DoxyPress is unaware of the STL classes, unless the option built-in-stl-support is turned on.
Please review the documentation regarding Overview.