⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 config.doc

📁 doxygen(一个自动从源代码生成文档的工具)的源代码
💻 DOC
📖 第 1 页 / 共 4 页
字号:
/****************************************************************************** * * $Id: config.doc,v 1.22 2001/03/19 19:27:39 root Exp $ * * Copyright (C) 1997-2001 by Dimitri van Heesch. * * Permission to use, copy, modify, and distribute this software and its * documentation under the terms of the GNU General Public License is hereby  * granted. No representations are made about the suitability of this software  * for any purpose. It is provided "as is" without express or implied warranty. * See the GNU General Public License for more details. * * Documents produced by Doxygen are derivative works derived from the * input used in their production; they are not affected by this license. * *//*! \page config Configuration\subsection config_format FormatA configuration file is a free-form ASCII text file with a structurethat is similar to that of a Makefile, default name \c Doxyfile. It isparsed by \c doxygen.  The file may contain tabs and newlines forformatting purposes.  The statements in the file are case-sensitive.Comments may be placed anywhere within the file (except within quotes).Comments begin with the \# character and end at the end of the line.The file essentially consists of a list of assignment statements.Each statement consists of a \c TAG_NAME written in capitals,followed by the <code>=</code> character and one or more values. If the same tagis assigned more than once, the last assignment overwrites any earlierassignment. For options that take a list as their argument,the <code>+=</code> operator can be used instead of <code>=</code> to append new values to the list. Values are sequences of non-blanks. If the value should contain one or more blanks it must be surrounded by quotes (&quot;...&quot;).Multiple lines can be concatenated by inserting a backslash (\\)as the last character of a line. Environment variables can be expanded using the pattern \c $(ENV_VARIABLE_NAME).You can also include part of a configuration file from another configurationfile using a <code>\@INCLUDE</code> tag as follows:\verbatim@INCLUDE = config_file_name\endverbatim The include file is searched in the current working directory. You can also specify a list of directories that should be searched before lookingin the current working directory. Do this by putting a <code>\@INCLUDE_PATH</code> tag with these paths before the <code>\@INCLUDE</code> tag, e.g:\verbatim@INCLUDE_PATH = my_config_dir\endverbatimThe configuration options can be divided into several categories.Below is an alphabetical index of the tags that are recognized followed by the descriptions of the tags grouped by category.\htmlonly<multicol cols=3><ul>\endhtmlonly\latexonly\footnotesize\begin{multicols}{2}\begin{CompactList}\endlatexonly<li> \refitem cfg_aliases ALIASES<li> \refitem cfg_allexternals ALLEXTERNALS <li> \refitem cfg_alphabetical_index ALPHABETICAL_INDEX <li> \refitem cfg_always_detailed_sec ALWAYS_DETAILED_SEC<li> \refitem cfg_bin_abspath BIN_ABSPATH <li> \refitem cfg_binary_toc BINARY_TOC<li> \refitem cfg_brief_member_desc BRIEF_MEMBER_DESC <li> \refitem cfg_case_sense_names CASE_SENSE_NAMES <li> \refitem cfg_cgi_name CGI_NAME <li> \refitem cfg_cgi_url CGI_URL <li> \refitem cfg_class_diagrams CLASS_DIAGRAMS <li> \refitem cfg_class_graph CLASS_GRAPH<li> \refitem cfg_collaboration_graph COLLABORATION_GRAPH<li> \refitem cfg_cols_in_alpha_index COLS_IN_ALPHA_INDEX<li> \refitem cfg_compact_latex COMPACT_LATEX <li> \refitem cfg_compact_rtf COMPACT_RTF<li> \refitem cfg_disable_index DISABLE_INDEX <li> \refitem cfg_distribute_group_doc DISTRIBUTE_GROUP_DOC<li> \refitem cfg_doc_abspath DOC_ABSPATH <li> \refitem cfg_doc_url DOC_URL<li> \refitem cfg_dot_path DOT_PATH<li> \refitem cfg_dotfile_dirs DOTFILE_DIRS<li> \refitem cfg_enable_preprocessing ENABLE_PREPROCESSING<li> \refitem cfg_enum_values_per_line ENUM_VALUES_PER_LINE<li> \refitem cfg_enabled_sections ENABLED_SECTIONS<li> \refitem cfg_example_path EXAMPLE_PATH<li> \refitem cfg_example_patterns EXAMPLE_PATTERNS<li> \refitem cfg_example_recursive EXAMPLE_RECURSIVE<li> \refitem cfg_exclude EXCLUDE<li> \refitem cfg_exclude_patterns EXCLUDE_PATTERNS<li> \refitem cfg_expand_as_defined EXPAND_AS_DEFINED<li> \refitem cfg_expand_only_predef EXPAND_ONLY_PREDEF<li> \refitem cfg_ext_doc_paths EXT_DOC_PATHS<li> \refitem cfg_extra_packages EXTRA_PACKAGES<li> \refitem cfg_extract_all EXTRACT_ALL<li> \refitem cfg_extract_private EXTRACT_PRIVATE<li> \refitem cfg_extract_static EXTRACT_STATIC<li> \refitem cfg_file_patterns FILE_PATTERNS<li> \refitem cfg_filter_source_files FILTER_SOURCE_FILES<li> \refitem cfg_full_path_names FULL_PATH_NAMES<li> \refitem cfg_generate_buglist GENERATE_BUGLIST<li> \refitem cfg_generate_chi GENERATE_CHI<li> \refitem cfg_generate_html GENERATE_HTML<li> \refitem cfg_generate_htmlhelp GENERATE_HTMLHELP<li> \refitem cfg_generate_latex GENERATE_LATEX<li> \refitem cfg_generate_legend GENERATE_LEGEND<li> \refitem cfg_generate_man GENERATE_MAN<li> \refitem cfg_generate_rtf GENERATE_RTF<li> \refitem cfg_generate_tagfile GENERATE_TAGFILE<li> \refitem cfg_generate_testlist GENERATE_TESTLIST<li> \refitem cfg_generate_todolist GENERATE_TODOLIST<li> \refitem cfg_generate_treeview GENERATE_TREEVIEW<li> \refitem cfg_graphical_hierarchy GRAPHICAL_HIERARCHY<li> \refitem cfg_have_dot HAVE_DOT<li> \refitem cfg_hide_scope_names HIDE_SCOPE_NAMES<li> \refitem cfg_hide_undoc_classes HIDE_UNDOC_CLASSES<li> \refitem cfg_hide_undoc_members HIDE_UNDOC_MEMBERS<li> \refitem cfg_hide_undoc_relations HIDE_UNDOC_RELATIONS<li> \refitem cfg_html_align_members HTML_ALIGN_MEMBERS<li> \refitem cfg_html_footer HTML_FOOTER<li> \refitem cfg_html_header HTML_HEADER<li> \refitem cfg_html_output HTML_OUTPUT<li> \refitem cfg_html_stylesheet HTML_STYLESHEET<li> \refitem cfg_ignore_prefix IGNORE_PREFIX<li> \refitem cfg_image_path IMAGE_PATH<li> \refitem cfg_include_graph INCLUDE_GRAPH<li> \refitem cfg_include_path INCLUDE_PATH<li> \refitem cfg_inherit_docs INHERIT_DOCS<li> \refitem cfg_inline_info INLINE_INFO<li> \refitem cfg_inline_sources INLINE_SOURCES<li> \refitem cfg_input INPUT<li> \refitem cfg_input_filter INPUT_FILTER<li> \refitem cfg_internal_docs INTERNAL_DOCS<li> \refitem cfg_javadoc_autobrief JAVADOC_AUTOBRIEF<li> \refitem cfg_latex_batchmode LATEX_BATCHMODE<li> \refitem cfg_latex_header LATEX_HEADER<li> \refitem cfg_latex_output LATEX_OUTPUT<li> \refitem cfg_macro_expansion MACRO_EXPANSION<li> \refitem cfg_man_extension MAN_EXTENSION<li> \refitem cfg_man_links MAN_LINKS<li> \refitem cfg_man_output MAN_OUTPUT<li> \refitem cfg_max_dot_graph_height MAX_DOT_GRAPH_HEIGHT<li> \refitem cfg_max_dot_graph_width MAX_DOT_GRAPH_WIDTH<li> \refitem cfg_max_initializer_lines MAX_INITIALIZER_LINES<li> \refitem cfg_optimize_output_for_c OPTIMIZE_OUTPUT_FOR_C<li> \refitem cfg_output_directory OUTPUT_DIRECTORY<li> \refitem cfg_output_language OUTPUT_LANGUAGE<li> \refitem cfg_paper_type PAPER_TYPE<li> \refitem cfg_pdf_hyperlinks PDF_HYPERLINKS<li> \refitem cfg_perl_path PERL_PATH<li> \refitem cfg_predefined PREDEFINED<li> \refitem cfg_project_name PROJECT_NAME<li> \refitem cfg_project_number PROJECT_NUMBER<li> \refitem cfg_quiet QUIET<li> \refitem cfg_recursive RECURSIVE<li> \refitem cfg_referenced_by_relation REFERENCED_BY_RELATION<li> \refitem cfg_references_relation REFERENCES_RELATION<li> \refitem cfg_repeat_brief REPEAT_BRIEF<li> \refitem cfg_rtf_extensions_file RTF_EXTENSIONS_FILE<li> \refitem cfg_rtf_hyperlinks RTF_HYPERLINKS<li> \refitem cfg_rtf_output RTF_OUTPUT<li> \refitem cfg_rtf_stylesheet_file RTF_STYLESHEET_FILE<li> \refitem cfg_search_includes SEARCH_INCLUDES<li> \refitem cfg_searchengine SEARCHENGINE<li> \refitem cfg_short_names SHORT_NAMES<li> \refitem cfg_show_include_files SHOW_INCLUDE_FILES<li> \refitem cfg_show_used_files SHOW_USED_FILES<li> \refitem cfg_skip_function_macros SKIP_FUNCTION_MACROS<li> \refitem cfg_sort_member_docs SORT_MEMBER_DOCS<li> \refitem cfg_source_browser SOURCE_BROWSER<li> \refitem cfg_strip_code_comments STRIP_CODE_COMMENTS<li> \refitem cfg_strip_from_path STRIP_FROM_PATH<li> \refitem cfg_tab_size TAB_SIZE<li> \refitem cfg_tagfiles TAGFILES<li> \refitem cfg_template_relations TEMPLATE_RELATIONS<li> \refitem cfg_toc_expand TOC_EXPAND<li> \refitem cfg_treeview_width TREEVIEW_WIDTH<li> \refitem cfg_verbatim_headers VERBATIM_HEADERS<li> \refitem cfg_warn_format WARN_FORMAT<li> \refitem cfg_warn_if_undocumented WARN_IF_UNDOCUMENTED<li> \refitem cfg_warn_logfile WARN_LOGFILE<li> \refitem cfg_warnings WARNINGS\htmlonly</ul></multicol>\endhtmlonly\latexonly\end{CompactList}\end{multicols}\normalsize\endlatexonly\subsection config_general General options\anchor cfg_project_name<dl><dt>\c PROJECT_NAME <dd> \addindex PROJECT_NAME The \c PROJECT_NAME tag is a single word (or a sequence of words surrounded by double-quotes) that should identify the project for which the  documentation is generated. This name is used in the title of most  generated pages and in a few other places.\anchor cfg_project_number<dt>\c PROJECT_NUMBER <dd> \addindex PROJECT_NUMBER The \c PROJECT_NUMBER tag can be used to enter a project or revision number. This could be handy for archiving the generated documentation or if some version control system is used.\anchor cfg_output_directory<dt>\c OUTPUT_DIRECTORY <dd>  \addindex OUTPUT_DIRECTORY The \c OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)  path into which the generated documentation will be written.  If a relative path is entered, it will be relative to the location  where doxygen was started. If left blank the current directory will be used.\anchor cfg_output_language<dt>\c OUTPUT_LANGUAGE <dd> \addindex OUTPUT_LANGUAGE The \c OUTPUT_LANGUAGE tag is used to specify the language in which all documentation generated by doxygen is written. Doxygen will use this information to generate all constant output in the proper language. The default language is English, other supported languages are: Dutch, French, Italian, Czech, Swedish, German, Finnish, Hungarian, Japanese, Korean, Spanish, Russian, Croatian, Polish and Portuguese.\anchor cfg_extract_all<dt>\c EXTRACT_ALL <dd> \addindex EXTRACT_ALL If the \c EXTRACT_ALL tag is set to \c YES doxygen will assume all  entities in documentation are documented, even if no documentation was  available. Private class members and static file members will be hidden  unless the \c EXTRACT_PRIVATE and \c EXTRACT_STATIC tags are set to \c YES \par Note:  This will also disable the warnings about undocumented members  that are normally produced when \c WARNINGS is set to \c YES\anchor cfg_extract_private<dt>\c EXTRACT_PRIVATE <dd> \addindex EXTRACT_PRIVATE If the \c EXTRACT_PRIVATE tag is set to \c YES all private members of a  class will be included in the documentation.\anchor cfg_extract_static<dt>\c EXTRACT_STATIC <dd> \addindex EXTRACT_STATIC If the \c EXTRACT_STATIC tag is set to \c YES all static members of a file will be included in the documentation.\anchor cfg_hide_undoc_members<dt>\c HIDE_UNDOC_MEMBERS <dd> \addindex HIDE_UNDOC_MEMBERS If the \c HIDE_UNDOC_MEMBERS tag is set to \c YES, doxygen will hide all undocumented members inside documented classes or files.  If set to \c NO (the default) these members will be included in the various overviews, but no documentation section is generated. This option has no effect if \c EXTRACT_ALL is enabled.\anchor cfg_hide_undoc_classes<dt>\c HIDE_UNDOC_CLASSES <dd> \addindex HIDE_UNDOC_CLASSES If the \c HIDE_UNDOC_CLASSESS tag is set to \c YES, doxygen will hide all undocumented classes. If set to \c NO (the default) these classes will be included in the various overviews. This option has no effect if \c EXTRACT_ALL is enabled.\anchor cfg_brief_member_desc<dt>\c BRIEF_MEMBER_DESC <dd> \addindex BRIEF_MEMBER_DESC If the \c BRIEF_MEMBER_DESC tag is set to \c YES (the default) doxygen will include brief member descriptions after the members that are listed in the file and class documentation (similar to JavaDoc). Set to NO to disable this.\anchor cfg_repeat_brief<dt>\c REPEAT_BRIEF <dd> \addindex REPEAT_BRIEF If the \c REPEAT_BRIEF tag is set to \c YES (the default) doxygen will  prepend the brief description of a member or function before the detailed  description  \par Note:  If both \c HIDE_UNDOC_MEMBERS and \c BRIEF_MEMBER_DESC are set to \c NO, the  brief descriptions will be completely suppressed.\anchor cfg_always_detailed_sec<dt>\c ALWAYS_DETAILED_SEC <dd> \addindex ALWAYS_DETAILED_SEC If the \c ALWAYS_DETAILED_SEC and \c REPEAT_BRIEF tags are both set to \c YES then doxygen will generate a detailed section even if there is only a brief description.\anchor cfg_full_path_names<dt>\c FULL_PATH_NAMES <dd> \addindex FULL_PATH_NAMES If the \c FULL_PATH_NAMES tag is set to \c YES doxygen will prepend the full path before files name in the file list and in the header files. If set to NO the shortest path that makes the file name unique will be used\anchor cfg_strip_from_path<dt>\c STRIP_FROM_PATH <dd> \addindex STRIP_FROM_PATH If the \c FULL_PATH_NAMES tag is set to \c YES then the \c STRIP_FROM_PATH tag can be used to strip a user defined part of the path. Stripping is only done if one of the specified strings matches the left-hand part of the  path.\anchor cfg_internal_docs<dt>\c INTERNAL_DOCS <dd> \addindex INTERNAL_DOCS The \c INTERNAL_DOCS tag determines if documentation that is typed after a \\internal command is included. If the tag is set to \c NO (the default) then the documentation will be excluded. Set it to \c YES to include the internal documentation.\anchor cfg_strip_code_comments<dt>\c STRIP_CODE_COMMENTS <dd> \addindex STRIP_CODE_COMMENTS Setting the \c STRIP_CODE_COMMENTS tag to \c YES (the default) will instruct doxygen to hide any special comment blocks from generated source code fragments. Normal C and C++ comments will always remain visible.\anchor cfg_case_sense_names<dt>\c CASE_SENSE_NAMES <dd> \addindex CASE_SENSE_NAMES If the \c CASE_SENSE_NAMES tag is set to \c NO (the default) then doxygen will only generate file names in lower case letters. If set to \c YES upper case letters are also allowed. This is useful if you have classes or files whose names only differ in case and if your file system supports case sensitive file names.\anchor cfg_short_names<dt>\c SHORT_NAMES <dd> \addindex SHORT_NAMES If the \c SHORT_NAMES tag is set to \c YES, doxygen will generate much shorter (but less readable) file names. This can be useful is your file systems doesn't support long names like on DOS, Mac, or CD-ROM.\anchor cfg_hide_scope_names<dt>\c HIDE_SCOPE_NAMES <dd> \addindex HIDE_SCOPE_NAMES If the \c HIDE_SCOPE_NAMES tag is set to \c NO (the default) then doxygen  will show members with their full class and namespace scopes in the documentation. If set to \c YES the scope will be hidden. \anchor cfg_verbatim_headers<dt>\c VERBATIM_HEADERS <dd> \addindex VERBATIM_HEADERS  If the \c VERBATIM_HEADERS tag is set the \c YES (the default) then doxygen  will generate a verbatim copy of the header file for each class for  which an include is specified. Set to NO to disable this.  \sa Section \ref cmdclass "\\class".

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -