The reader is referred to the Markdown site for more details. In the next section the standard Markdown features are briefly discussed. While Markdown's syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown's syntax is the format of plain text email. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it's been marked up with tags or formatting instructions. The design goal for Markdown's formatting syntax is to make it as readable as possible. It is a plain text formatting syntax written by John Gruber, with the following underlying design goal: Enabling this option can be useful when feeding doxygen a huge amount of source files, where putting all generated files in the same directory would otherwise causes performance problems for the file system.Markdown support was introduced in doxygen version 1.8.0. If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096 sub-directories (in 2 levels) under the output directory of each output format and will distribute the generated files over these directories. If left blank the current directory will be used. If a relative path is entered, it will be relative to the location where doxygen was started. The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path into which the generated documentation will be written. Doxygen will copy the logo to the output directory. The maximum height of the logo should not exceed 55 pixels and the maximum width should not exceed 200 pixels. With the PROJECT_LOGO tag one can specify a logo or an icon that is included in the documentation. Using the PROJECT_BRIEF tag one can provide an optional one line description for a project that appears at the top of each page and should give viewer a quick idea about the purpose of the project. This could be handy for archiving the generated documentation or if some version control system is used. The PROJECT_NUMBER tag can be used to enter a project or revision number. This name is used in the title of most generated pages and in a few other places. The PROJECT_NAME tag is a single word (or a sequence of words surrounded by double-quotes, unless you are using Doxywizard) that should identify the project for which the documentation is generated. Doxygen uses libiconv (or the iconv built into libc) for the transcoding. The default is UTF-8 which is also the encoding used for all text before the first occurrence of this tag. This tag specifies the encoding used for all characters in the configuration file that follow. Below is an alphabetical index of the tags that are recognized followed by the descriptions of the tags grouped by category. The configuration options can be divided into several categories. Do this by putting a tag with these paths before the tag, e.g.: = my_config_dir You can also specify a list of directories that should be searched before looking in the current working directory. The include file is searched in the current working directory. You can also include part of a configuration file from another configuration file using a tag as follows: = config_file_name A small example: DOT_PATH = $(YOUR_DOT_PATH) Multiple lines can be concatenated by inserting a backslash ( \) as the last character of a line.Įnvironment variables can be expanded using the pattern $(ENV_VARIABLE_NAME). If the value should contain one or more blanks it must be surrounded by quotes ( "."). For tags that take a list as their argument, the = operator can be used instead of = to append new values to the list. If the same tag is assigned more than once, the last assignment overwrites any earlier assignment. Each statement consists of a TAG_NAME written in capitals, followed by the equal sign ( =) and one or more values. The file essentially consists of a list of assignment statements. Comments begin with the hash character ( #) and ends at the end of the line. Comments beginning with two hash characters ( #) at the end of the configuration file are also kept and placed at the end of the file. Comments beginning with two hash characters ( #) at the beginning of the configuration file are also kept and placed at the beginning of the file. Comments beginning with two hash characters ( #) are kept when updating the configuration file and are placed in front of the TAG they are in front of. Comments may be placed anywhere within the file (except within quotes). The statements in the file are case-sensitive. The file may contain tabs and newlines for formatting purposes. A configuration file is a free-form ASCII text file with a structure that is similar to that of a Makefile, with the default name Doxyfile.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |