# Boost-Commit :

Subject: [Boost-commit] svn:boost r73933 - sandbox/SOC/2011/checks/libs/checks/doc/doxygen
From: pierre.talbot.6114_at_[hidden]
Date: 2011-08-19 19:53:32

Date: 2011-08-19 19:53:31 EDT (Fri, 19 Aug 2011)
New Revision: 73933
URL: http://svn.boost.org/trac/boost/changeset/73933

Log:
Minor changes.
Text files modified:
sandbox/SOC/2011/checks/libs/checks/doc/doxygen/Doxyfile.txt | 80 ++++++++++------------------------------
1 files changed, 20 insertions(+), 60 deletions(-)

Modified: sandbox/SOC/2011/checks/libs/checks/doc/doxygen/Doxyfile.txt
==============================================================================
--- sandbox/SOC/2011/checks/libs/checks/doc/doxygen/Doxyfile.txt (original)
+++ sandbox/SOC/2011/checks/libs/checks/doc/doxygen/Doxyfile.txt 2011-08-19 19:53:31 EDT (Fri, 19 Aug 2011)
@@ -1,4 +1,4 @@
-# Doxyfile 1.7.5
+# Doxyfile 1.7.4

# This file describes the settings to be used by the documentation system
# doxygen (www.doxygen.org) for a project
@@ -22,11 +22,10 @@

DOXYFILE_ENCODING = UTF-8

-# The PROJECT_NAME tag is a single word (or sequence of words) that should
-# identify the project. Note that if you do not use Doxywizard you need
-# to put quotes around the project name if it contains spaces.
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
+# by quotes) that should identify the project.

-PROJECT_NAME = Checks
+PROJECT_NAME = Boost.Checks

# The PROJECT_NUMBER tag can be used to enter a project or revision number.
# This could be handy for archiving the generated documentation or
@@ -294,15 +293,6 @@

INLINE_GROUPED_CLASSES = NO

-# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
-# unions with only public data fields will be shown inline in the documentation
-# of the scope in which they are defined (i.e. file, namespace, or group
-# documentation), provided this scope is documented. If set to NO (the default),
-# structs, classes, and unions are shown on a separate page (for HTML and Man
-# pages) or section (for LaTeX and RTF).
-
-INLINE_SIMPLE_STRUCTS = NO
-
# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
# is documented as struct, union, or enum with the name of the typedef. So
# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
@@ -569,15 +559,6 @@

LAYOUT_FILE =

-# The CITE_BIB_FILES tag can be used to specify one or more bib files
-# containing the references data. This must be a list of .bib files. The
-# .bib extension is automatically appended if omitted. Using this command
-# requires the bibtex tool to be installed. See also
-# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
-# of the bibliography can be controlled using LATEX_BIB_STYLE.
-
-CITE_BIB_FILES =
-
#---------------------------------------------------------------------------
# configuration options related to warning and progress messages
#---------------------------------------------------------------------------
@@ -664,12 +645,11 @@
# should be searched for input files as well. Possible values are YES and NO.
# If left blank NO is used.

-RECURSIVE = NO
+RECURSIVE = YES

# The EXCLUDE tag can be used to specify files and/or directories that should
# excluded from the INPUT source files. This way you can easily exclude a
-# subdirectory from a directory tree whose root is specified with the INPUT tag.
-# Note that relative paths are relative to directory from which doxygen is run.
+# subdirectory from a directory tree whose root is specified with the INPUT tag.

EXCLUDE =

@@ -855,13 +835,13 @@

# The HTML_HEADER tag can be used to specify a personal HTML header for
# each generated HTML page. If it is left blank doxygen will generate a
-# standard header. Note that when using a custom header you are responsible
+# standard header. Note that when using a custom header you are responsible
# for the proper inclusion of any scripts and style sheets that doxygen
# needs, which is dependent on the configuration options used.
# It is adviced to generate a default header using "doxygen -w html
# header.html footer.html stylesheet.css YourConfigFile" and then modify
# that header. Note that the header is subject to change so you typically
-# have to redo this when upgrading to a newer version of doxygen or when
+# have to redo this when upgrading to a newer version of doxygen or when
# changing the value of configuration settings such as GENERATE_TREEVIEW!

@@ -1161,11 +1141,6 @@

MATHJAX_RELPATH = http://www.mathjax.org/mathjax

-# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
-# names that should be enabled during MathJax rendering.
-
-MATHJAX_EXTENSIONS =
-
# When the SEARCHENGINE tag is enabled doxygen will generate a search box
# for the HTML output. The underlying search engine uses javascript
# and DHTML and should work on any modern browser. Note that when using
@@ -1279,12 +1254,6 @@

LATEX_SOURCE_CODE = NO

-# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
-# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
-
-LATEX_BIB_STYLE = plain
-
#---------------------------------------------------------------------------
# configuration options related to the RTF output
#---------------------------------------------------------------------------
@@ -1586,12 +1555,13 @@

-# By default doxygen will use the Helvetica font for all dot files that
-# doxygen generates. When you want a differently looking font you can specify
-# the font name using DOT_FONTNAME. You need to make sure dot is able to find
-# the font, which can be done by putting it in a standard location or by setting
-# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
-# directory containing the font.
+# By default doxygen will write a font called Helvetica to the output
+# directory and reference it in all dot files that doxygen generates.
+# When you want a differently looking font you can specify the font name
+# using DOT_FONTNAME. You need to make sure dot is able to find the font,
+# which can be done by putting it in a standard location or by setting the
+# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
+# containing the font.

DOT_FONTNAME = Helvetica

@@ -1600,9 +1570,10 @@

DOT_FONTSIZE = 10

-# By default doxygen will tell dot to use the Helvetica font.
-# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to
-# set the path where dot can find it.
+# By default doxygen will tell dot to use the output directory to look for the
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a
+# different font using DOT_FONTNAME you can set the path where dot
+# can find it using this tag.

DOT_FONTPATH =

@@ -1680,21 +1651,10 @@

# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
# generated by dot. Possible values are svg, png, jpg, or gif.
-# If left blank png will be used. If you choose svg you need to set
-# HTML_FILE_EXTENSION to xhtml in order to make the SVG files
-# visible in IE 9+ (other browsers do not have this requirement).
+# If left blank png will be used.

DOT_IMAGE_FORMAT = png

-# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
-# enable generation of interactive SVG images that allow zooming and panning.
-# Note that this requires a modern browser other than Internet Explorer.
-# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
-# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files
-# visible. Older versions of IE do not have SVG support.
-
-INTERACTIVE_SVG = NO
-
# The tag DOT_PATH can be used to specify the path where the dot tool can be
# found. If left blank, it is assumed the dot tool can be found in the path.