|
|
@ -17,13 +17,13 @@
|
|
|
|
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
|
|
|
|
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
|
|
|
|
# by quotes) that should identify the project.
|
|
|
|
# by quotes) that should identify the project.
|
|
|
|
|
|
|
|
|
|
|
|
PROJECT_NAME = Asterisk
|
|
|
|
PROJECT_NAME = "Asterisk - the Open Source PBX"
|
|
|
|
|
|
|
|
|
|
|
|
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
|
|
|
|
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
|
|
|
|
# This could be handy for archiving the generated documentation or
|
|
|
|
# This could be handy for archiving the generated documentation or
|
|
|
|
# if some version control system is used.
|
|
|
|
# if some version control system is used.
|
|
|
|
|
|
|
|
|
|
|
|
PROJECT_NUMBER = CVS
|
|
|
|
PROJECT_NUMBER = CVS_HEAD
|
|
|
|
|
|
|
|
|
|
|
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
|
|
|
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
|
|
|
|
# base path where the generated documentation will be put.
|
|
|
|
# base path where the generated documentation will be put.
|
|
|
@ -500,7 +500,9 @@ EXCLUDE_PATTERNS =
|
|
|
|
# directories that contain example code fragments that are included (see
|
|
|
|
# directories that contain example code fragments that are included (see
|
|
|
|
# the \include command).
|
|
|
|
# the \include command).
|
|
|
|
|
|
|
|
|
|
|
|
EXAMPLE_PATH =
|
|
|
|
EXAMPLE_PATH = ./ \
|
|
|
|
|
|
|
|
doc \
|
|
|
|
|
|
|
|
configs
|
|
|
|
|
|
|
|
|
|
|
|
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
|
|
|
|
# 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
|
|
|
|
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
|
|
|
@ -520,7 +522,7 @@ EXAMPLE_RECURSIVE = NO
|
|
|
|
# directories that contain image that are included in the documentation (see
|
|
|
|
# directories that contain image that are included in the documentation (see
|
|
|
|
# the \image command).
|
|
|
|
# the \image command).
|
|
|
|
|
|
|
|
|
|
|
|
IMAGE_PATH =
|
|
|
|
IMAGE_PATH = images
|
|
|
|
|
|
|
|
|
|
|
|
# The INPUT_FILTER tag can be used to specify a program that doxygen should
|
|
|
|
# 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
|
|
|
|
# invoke to filter for each input file. Doxygen will invoke the filter program
|
|
|
@ -635,7 +637,7 @@ HTML_FILE_EXTENSION = .html
|
|
|
|
# each generated HTML page. If it is left blank doxygen will generate a
|
|
|
|
# each generated HTML page. If it is left blank doxygen will generate a
|
|
|
|
# standard header.
|
|
|
|
# standard header.
|
|
|
|
|
|
|
|
|
|
|
|
HTML_HEADER =
|
|
|
|
HTML_HEADER = contrib/asterisk-doxygen-header
|
|
|
|
|
|
|
|
|
|
|
|
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
|
|
|
|
# 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
|
|
|
|
# each generated HTML page. If it is left blank doxygen will generate a
|
|
|
|