Blog

2 minutes read
To change Doxygen to not use any file extension, you need to modify the configuration file. In the Doxygen configuration file, you can specify the file patterns that Doxygen should consider as input files. By removing the file extension from the list of accepted file patterns, you can make Doxygen process files without any extension. This allows you to include files that do not have an extension or have a different extension than what Doxygen typically expects.
6 minutes read
To properly document a specialized C++ constructor with Doxygen, you should provide detailed comments within the constructor itself. This includes information about the purpose of the constructor, any parameters it accepts, and what it initializes or modifies. Additionally, you can use Doxygen-specific tags such as @brief, @param, @return, and @see to provide further context and links to related elements in your code documentation.
4 minutes read
In Doxygen, you can regenerate the class URL by deleting the HTML output for that specific class and then running the Doxygen generation process again. This will update the URL for the class in the output HTML files. You can also use the 'GENERATE_HTML' and 'GENERATE_LATEX' options in the Doxygen configuration file to control which types of output are generated when regenerating the documentation.How to access the Doxygen documentation generator.
3 minutes read
To exclude a method inside a class with Doxygen, you can use the \cond and \endcond commands. These commands are used to toggle the inclusion of specific parts of the code in the generated documentation. Simply wrap the method you want to exclude between these commands, and it will not be documented when you generate the output. This can be useful if you have certain methods that are private or internal and do not need to be included in the documentation.
5 minutes read
To ignore generated code in Doxygen, you can use the EXCLUDE_PATTERNS option in the Doxygen configuration file. This option allows you to specify patterns for files or directories that should be excluded from the documentation generation process. By adding the file names or directory names containing the generated code to the EXCLUDE_PATTERNS option, you can prevent Doxygen from documenting those files or directories.
5 minutes read
To change the config file for MathJax in Doxygen, you will need to locate the MathJax configuration file within your Doxygen project. This file is typically named MathJax.js and is located in the Doxygen's output directory. You can then edit this file to customize the MathJax settings according to your requirements.
3 minutes read
To use Doxygen with Prolog, you can first add Doxygen-style comments to your Prolog code. These comments typically start with /** and end with */, and can include special command tags like @param and @return to document the function parameters and return values.You can then run Doxygen on your Prolog code to generate the documentation. This can be done by creating a Doxyfile configuration file specifying the input files and any additional settings you want to include in the documentation.
2 minutes read
In Doxygen markdown, you can create a line break by leaving a blank line between two lines of text. This will create a clear separation between the two lines, making it easier for readers to understand the content. Additionally, you can also use the <br> tag to create a line break within a single line of text. Simply add <br> where you want the line break to occur, and Doxygen will render it accordingly.
4 minutes read
To preserve a comment in an example in Doxygen, use the tag before and after the comment. This will display the text exactly as it is written without any formatting or special characters being interpreted. This can be useful when you want to include code snippets or special characters in your comments without them being modified by Doxygen.What is the process for controlling example visibility in Doxygen.
3 minutes read
In order to use relative path names in the Doxygen configuration, the user must specify the path relative to the location of the configuration file. This can be done by using the "../" notation to navigate up one directory level, and then specify the path to the desired file or folder. By using relative paths, the configuration file can be easily moved without needing to update all the paths within the file.