3
# This file describes the settings to be used by doxygen for a project
5
# All text after a hash (#) is considered a comment and will be ignored
7
# TAG = value [value, ...]
8
# For lists items can also be appended using:
9
# TAG += value [value, ...]
10
# Values that contain spaces should be placed between quotes (" ")
13
# Include the standard part of the doxygen configuration:
16
@INCLUDE_PATH = @prefix@/share/doxygen
18
@INCLUDE = Doxyfile.include
20
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
21
# by quotes) that should identify the project.
23
PROJECT_NAME = "@lac_doxygen_project@"
25
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
26
# This could be handy for archiving the generated documentation or
27
# if some version control system is used.
29
PROJECT_NUMBER = @VERSION@
31
# The INPUT tag can be used to specify the files and/or directories that contain
32
# documented source files. You may enter file names like "myfile.cpp" or
33
# directories like "/usr/src/myproject". Separate the files or directories
36
INPUT = @lac_doxygen_srcdirs@ \
37
@lac_doxygen_examples@
39
# If the value of the INPUT tag contains directories, you can use the
40
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
41
# and *.h) to filter out the source-files in the directories. If left
42
# blank all files are included.
46
@lac_doxygen_file_patterns@
48
# The INPUT_FILTER tag can be used to specify a program that doxygen should
49
# invoke to filter for each input file. Doxygen will invoke the filter program
50
# by executing (via popen()) the command <filter> <input-file>, where <filter>
51
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
52
# input file. Doxygen will then use the output that the filter program writes
55
INPUT_FILTER = @lac_doxygen_input_filter@
57
# The EXAMPLE_PATH tag can be used to specify one or more files or
58
# directories that contain example code fragments that are included (see
59
# the \include command).
61
EXAMPLE_PATH = @lac_doxygen_examples@
63
# The HTML_HEADER tag can be used to specify a personal HTML header for
64
# each generated HTML page. If it is left blank doxygen will generate a
67
HTML_HEADER = @prefix@/share/doxygen/globus_head.html
69
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
70
# each generated HTML page. If it is left blank doxygen will generate a
73
HTML_FOOTER = @prefix@/share/doxygen/globus_foot.html
75
# The HTML_STYLESHEET tag can be used to specify a user defined cascading
76
# style sheet that is used by each HTML page. It can be used to
77
# fine-tune the look of the HTML output. If the tag is left blank doxygen
78
# will generate a default style sheet
80
HTML_STYLESHEET = @prefix@/share/doxygen/globus.css
82
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
83
# the generated latex document. The header should contain everything until
84
# the first chapter. If it is left blank doxygen will generate a
85
# standard header. Notice: only use this tag if you know what you are doing!
87
LATEX_HEADER = @prefix@/share/doxygen/globus_head.tex
89
# The PREDEFINED tag can be used to specify one or more macro names that
90
# are defined before the preprocessor is started (similar to the -D option of
91
# gcc). The argument of the tag is a list of macros of the form: name
92
# or name=definition (no spaces). If the definition and the = are
93
# omitted =1 is assumed.
95
PREDEFINED = GLOBUS_DONT_DOCUMENT_INTERNAL \
96
GLOBUS_SEPARATE_DOCS \
98
@lac_doxygen_predefines@
100
# The TAGFILES tag can be used to specify one or more tagfiles.
102
TAGFILES = @lac_doxygen_tagfiles@
104
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
105
# a tag file that is based on the input files it reads.
107
GENERATE_TAGFILE = doc/html/@lac_doxygen_output_tagfile@.tag
109
# The PERL_PATH should be the absolute path and name of the perl script
110
# interpreter (i.e. the result of `which perl').
114
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
115
# available from the path. This tool is part of Graphviz, a graph visualization
116
# toolkit from AT&T and Lucent Bell Labs. The other options in this section
117
# have no effect if this option is set to NO (the default)
119
HAVE_DOT = @HAVE_DOT@
121
# The DOTFILE_DIRS tag can be used to specify one or more directories that
122
# contain dot files that are included in the documentation (see the
125
DOTFILE_DIRS = @lac_doxygen_srcdirs@ \
126
@lac_doxygen_examples@
added
removed
doxygen/Doxyfile.in
