diff options
| -rw-r--r-- | docs/doxygen.cfg | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/doxygen.cfg b/docs/doxygen.cfg index 3f94913fd4..40180b2415 100644 --- a/docs/doxygen.cfg +++ b/docs/doxygen.cfg @@ -23,14 +23,14 @@ PROJECT_NAME = clang # This could be handy for archiving the generated documentation or # if some version control system is used. -PROJECT_NUMBER = 3.0svn +PROJECT_NUMBER = mainline # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) # base path where the generated documentation will be put. # 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. -OUTPUT_DIRECTORY = /Volumes/Ebi/echeng/llvm/tools/clang/docs/doxygen +OUTPUT_DIRECTORY = ../docs/doxygen # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create # 4096 sub-directories (in 2 levels) under the output directory of each output @@ -450,9 +450,9 @@ WARN_LOGFILE = # directories like "/usr/src/myproject". Separate the files or directories # with spaces. -INPUT = /Volumes/Ebi/echeng/llvm/tools/clang/docs/../include \ - /Volumes/Ebi/echeng/llvm/tools/clang/docs/../lib \ - /Volumes/Ebi/echeng/llvm/tools/clang/docs/doxygen.intro +INPUT = ../include \ + ../lib \ + ../docs/doxygen.intro # 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 @@ -493,7 +493,7 @@ EXCLUDE_PATTERNS = # directories that contain example code fragments that are included (see # the \include command). -EXAMPLE_PATH = /Volumes/Ebi/echeng/llvm/tools/clang/docs/../examples +EXAMPLE_PATH = ../examples # If the value of the EXAMPLE_PATH tag contains directories, you can use the # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp @@ -513,7 +513,7 @@ EXAMPLE_RECURSIVE = YES # directories that contain image that are included in the documentation (see # the \image command). -IMAGE_PATH = /Volumes/Ebi/echeng/llvm/tools/clang/docs/img +IMAGE_PATH = ../docs/img # The INPUT_FILTER tag can be used to specify a program that doxygen should # invoke to filter for each input file. Doxygen will invoke the filter program @@ -609,7 +609,7 @@ COLS_IN_ALPHA_INDEX = 4 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that # should be ignored while generating the index headers. -IGNORE_PREFIX = clang:: +IGNORE_PREFIX = llvm:: #--------------------------------------------------------------------------- # configuration options related to the HTML output @@ -636,13 +636,13 @@ HTML_FILE_EXTENSION = .html # each generated HTML page. If it is left blank doxygen will generate a # standard header. -HTML_HEADER = /Volumes/Ebi/echeng/llvm/tools/clang/docs/doxygen.header +HTML_HEADER = ../docs/doxygen.header # The HTML_FOOTER tag can be used to specify a personal HTML footer for # each generated HTML page. If it is left blank doxygen will generate a # standard footer. -HTML_FOOTER = /Volumes/Ebi/echeng/llvm/tools/clang/docs/doxygen.footer +HTML_FOOTER = ../docs/doxygen.footer # The HTML_STYLESHEET tag can be used to specify a user-defined cascading # style sheet that is used by each HTML page. It can be used to @@ -651,7 +651,7 @@ HTML_FOOTER = /Volumes/Ebi/echeng/llvm/tools/clang/docs/doxygen.foote # the style sheet file to the HTML output directory, so don't put your own # stylesheet in the HTML output directory as well, or it will be erased! -HTML_STYLESHEET = /Volumes/Ebi/echeng/llvm/tools/clang/docs/doxygen.css +HTML_STYLESHEET = ../docs/doxygen.css # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, # files or namespaces will be aligned in HTML using tables. If set to @@ -1157,7 +1157,7 @@ DOT_IMAGE_FORMAT = png # 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. -DOT_PATH = /usr/local/bin/dot +DOT_PATH = dot # The DOTFILE_DIRS tag can be used to specify one or more directories that # contain dot files that are included in the documentation (see the |