Author: wyoung
Date: Fri Apr 13 16:21:45 2007
New Revision: 1521
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=1521&view=rev
Log:
Updated lib/Doxyfile.in for Doxygen 1.5.2
Modified:
trunk/lib/Doxyfile.in
Modified: trunk/lib/Doxyfile.in
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/lib/Doxyfile.in?rev=1521&r1=1520&r2=1521&view=diff
==============================================================================
--- trunk/lib/Doxyfile.in (original)
+++ trunk/lib/Doxyfile.in Fri Apr 13 16:21:45 2007
@@ -1,4 +1,4 @@
-# Doxyfile 1.5.1-3
+# Doxyfile 1.5.2-1
# This file describes the settings to be used by the documentation system
# doxygen (www.doxygen.org) for a project
@@ -14,6 +14,14 @@
# Project related configuration options
#---------------------------------------------------------------------------
+# This tag specifies the encoding used for all characters in the config file
that
+# follow. The default is UTF-8 which is also the encoding used for all text
before
+# the first occurrence of this tag. Doxygen uses libiconv (or the iconv built
into
+# libc) for the transcoding. See http://www.gnu.org/software/libiconv for the
list of
+# possible encodings.
+
+DOXYFILE_ENCODING = UTF-8
+
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
# by quotes) that should identify the project.
@@ -53,16 +61,6 @@
OUTPUT_LANGUAGE = English
-# This tag can be used to specify the encoding used in the generated output.
-# The encoding is not always determined by the language that is chosen,
-# but also whether or not the output is meant for Windows or non-Windows
users.
-# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
-# forces the Windows encoding (this is the default for the Windows binary),
-# whereas setting the tag to NO uses a Unix-style encoding (the default for
-# all platforms other than Windows).
-
-USE_WINDOWS_ENCODING = NO
-
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
# include brief member descriptions after the members that are listed in
# the file and class documentation (similar to JavaDoc).
@@ -466,6 +464,13 @@
INPUT =
+# This tag can be used to specify the character encoding of the source files
that
+# doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also
the default
+# input encoding. Doxygen uses libiconv (or the iconv built into libc) for the
transcoding.
+# See http://www.gnu.org/software/libiconv for the list of possible encodings.
+
+INPUT_ENCODING = UTF-8
+
# If the value of the INPUT tag contains directories, you can use the
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
# and *.h) to filter out the source-files in the directories. If left
@@ -501,6 +506,13 @@
# for example use the pattern */test/*
EXCLUDE_PATTERNS =
+
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
+# (namespaces, classes, functions, etc.) that should be excluded from the
output.
+# The symbol name can be a fully qualified name, a word, or if the wildcard *
is used,
+# a substring. Examples: ANamespace, AClass, AClass::ANamespace,
ANamespace::*Test
+
+EXCLUDE_SYMBOLS =
# The EXAMPLE_PATH tag can be used to specify one or more files or
# directories that contain example code fragments that are included (see
@@ -1091,6 +1103,14 @@
CLASS_DIAGRAMS = YES
+# You can define message sequence charts within doxygen comments using the
\msc
+# command. Doxygen will then run the mscgen tool (see
http://www.mcternan.me.uk/mscgen/) to
+# produce the chart and insert it in the documentation. The MSCGEN_PATH tag
allows you to
+# specify the directory where the mscgen tool resides. If left empty the tool
is assumed to
+# be found in the default search path.
+
+MSCGEN_PATH =
+
# If set to YES, the inheritance and collaboration graphs will hide
# inheritance and usage relations if the target is undocumented
# or is not a class.
_______________________________________________
Mysqlpp-commits mailing list
[EMAIL PROTECTED]
https://mail.gna.org/listinfo/mysqlpp-commits
