# interpret the first line (until the first dot) of a Qt-style
# comment as the brief description. If set to NO, the comments
# will behave just like regular Qt-style comments (thus requiring
-# an explicit \brief command for a brief description.)
+# an explicit @brief command for a brief description.)
QT_AUTOBRIEF = NO
@CMAKE_HOME_DIRECTORY@/doc/doxygen/outcomes_logs.doc \
@CMAKE_HOME_DIRECTORY@/doc/doxygen/outcomes_vizu.doc \
@CMAKE_HOME_DIRECTORY@/doc/doxygen/outcomes_MC.doc \
- @CMAKE_HOME_DIRECTORY@/doc/tuto-msg/tuto-msg.doc \
@CMAKE_HOME_DIRECTORY@/doc/doxygen/tutorial_smpi.doc \
@CMAKE_HOME_DIRECTORY@/doc/doxygen/examples.doc \
@CMAKE_HOME_DIRECTORY@/doc/doxygen/howtos.doc \
@CMAKE_HOME_DIRECTORY@/doc/doxygen/module-trace.doc \
@CMAKE_BINARY_DIR@/doc/doxygen/logcategories.doc \
@CMAKE_HOME_DIRECTORY@/include/ \
- @CMAKE_HOME_DIRECTORY@/include/xbt \
- @CMAKE_HOME_DIRECTORY@/include/simgrid \
- @CMAKE_HOME_DIRECTORY@/include/simgrid/s4u \
- @CMAKE_HOME_DIRECTORY@/src/include/surf \
- @CMAKE_HOME_DIRECTORY@/src/include/xbt \
- @CMAKE_HOME_DIRECTORY@/src/msg/ \
- @CMAKE_HOME_DIRECTORY@/src/kernel/ \
- @CMAKE_HOME_DIRECTORY@/src/kernel/activity/ \
- @CMAKE_HOME_DIRECTORY@/src/kernel/context/ \
- @CMAKE_HOME_DIRECTORY@/src/kernel/routing/ \
- @CMAKE_HOME_DIRECTORY@/src/instr/ \
- @CMAKE_HOME_DIRECTORY@/src/surf/ \
- @CMAKE_HOME_DIRECTORY@/src/surf/plugins/ \
- @CMAKE_HOME_DIRECTORY@/src/s4u/ \
- @CMAKE_HOME_DIRECTORY@/src/smpi/ \
- @CMAKE_HOME_DIRECTORY@/src/simdag \
- @CMAKE_HOME_DIRECTORY@/src/simix \
- @CMAKE_HOME_DIRECTORY@/src/xbt/ \
- @CMAKE_BINARY_DIR@/include \
- @CMAKE_BINARY_DIR@/src \
- @CMAKE_HOME_DIRECTORY@/examples/msg/README.doc \
+ @CMAKE_HOME_DIRECTORY@/src/plugins/ \
+ @CMAKE_HOME_DIRECTORY@/examples/deprecated/msg/README.doc \
@CMAKE_HOME_DIRECTORY@/examples/s4u/README.doc
+
# 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
# Note that relative paths are relative to the directory from which doxygen is
# run.
-EXCLUDE =
+EXCLUDE =
# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
# directories that are symbolic links (a Unix file system feature) are excluded
# against the file with absolute path, so to exclude all test directories
# for example use the pattern */test/*
-EXCLUDE_PATTERNS =
+EXCLUDE_PATTERNS = */include/simgrid/forward.h
+EXCLUDE_PATTERNS += */include/smpi/*
+
+EXCLUDE_PATTERNS += @CMAKE_HOME_DIRECTORY@/src/surf/xml/simgrid_dtd.*
+EXCLUDE_PATTERNS += @CMAKE_HOME_DIRECTORY@/src/simdag/dax_dtd.*
+EXCLUDE_PATTERNS += @CMAKE_HOME_DIRECTORY@/src/xbt/automaton/parserPromela.*
+EXCLUDE_PATTERNS += @CMAKE_HOME_DIRECTORY@/src/bindings/java/*.cpp @CMAKE_HOME_DIRECTORY@/src/bindings/java/*.h
+EXCLUDE_PATTERNS += @CMAKE_HOME_DIRECTORY@/src/simix/popping_accessors.hpp \
+ @CMAKE_HOME_DIRECTORY@/src/simix/popping_bodies.cpp \
+ @CMAKE_HOME_DIRECTORY@/src/simix/popping_enum.h \
+ @CMAKE_HOME_DIRECTORY@/src/simix/popping_generated.cpp
+
# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
# (namespaces, classes, functions, etc.) that should be excluded from the
# wildcard * is used, a substring. Examples: ANamespace, AClass,
# AClass::ANamespace, ANamespace::*Test
-EXCLUDE_SYMBOLS =
+EXCLUDE_SYMBOLS = s_xbt_dict_cursor s_xbt_dictelm xbt_dynar_s
+EXCLUDE_SYMBOLS += xbt_edge xbt_graph xbt_node
+EXCLUDE_SYMBOLS += e_xbt_parmap_mode_t
+EXCLUDE_SYMBOLS += MPI_*
# The EXAMPLE_PATH tag can be used to specify one or more files or
# directories that contain example code fragments that are included (see
@CMAKE_HOME_DIRECTORY@/src/xbt/ \
@CMAKE_HOME_DIRECTORY@/include \
@CMAKE_HOME_DIRECTORY@/examples \
- @CMAKE_BINARY_DIR@/doc/example_lists \
- @CMAKE_HOME_DIRECTORY@/doc/tuto-msg
+ @CMAKE_BINARY_DIR@/doc/example_lists
# 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
HTML_FILE_EXTENSION = .html
-# 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
-# for the proper inclusion of any scripts and style sheets that doxygen
-# needs, which is dependent on the configuration options used.
-# It is advised 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
-# changing the value of configuration settings such as GENERATE_TREEVIEW!
-
-HTML_HEADER = @CMAKE_HOME_DIRECTORY@/doc/doxygen/header.html
-
-# 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 = @CMAKE_HOME_DIRECTORY@/doc/doxygen/footer.html
-
# 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
# fine-tune the look of the HTML output. If the tag is left blank doxygen
# generate an XML file that captures the structure of
# the code including all documentation.
-GENERATE_XML = NO
+GENERATE_XML = YES
#---------------------------------------------------------------------------
# configuration options for the AutoGen Definitions output
# undefined via #undef or recursively expanded use the := operator
# instead of the = operator.
-PREDEFINED = XBT_PUBLIC= \
+PREDEFINED = __cplusplus \
+ DOXYGEN \
+ XBT_PUBLIC= \
XBT_EXPORT_NO_IMPORT= \
XBT_IMPORT_NO_EXPORT= \
XBT_PUBLIC_DATA=extern \
+ XBT_PUBLIC= \
XBT_INLINE= \
+ XBT_ALWAYS_INLINE= \
XBT_PRIVATE= \
- XBT_ATTRIB_DEPRECATED_v321(m)= \
- XBT_ATTRIB_DEPRECATED_v322(m)= \
- XBT_ATTRIB_DEPRECATED_v323(m)=
+ XBT_ATTRIB_NORETURN= \
+ XBT_ATTRIB_UNUSED= \
+ XBT_ATTRIB_DEPRECATED_v325(m)= \
+ XBT_ATTRIB_DEPRECATED_v327(m)=
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
# this tag can be used to specify a list of macro names that should be expanded.
# Use the PREDEFINED tag if you want to use a different macro definition that
# overrules the definition found in the source code.
-EXPAND_AS_DEFINED =
+EXPAND_AS_DEFINED = COLL_APPLY COLL_GATHERS COLL_ALLGATHERS COLL_ALLGATHERVS COLL_ALLREDUCES COLL_ALLTOALLS \
+ COLL_ALLTOALLVS COLL_BCASTS COLL_REDUCES COLL_REDUCE_SCATTERS COLL_SCATTERS COLL_BARRIERS \
+ MPI_CALL
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
# doxygen's preprocessor will remove all references to function-like macros
# this option also works with HAVE_DOT disabled, but it is recommended to
# install and use dot, since it yields more powerful graphs.
-CLASS_DIAGRAMS = YES
+CLASS_DIAGRAMS = NO
# You can define message sequence charts within doxygen comments using the \msc
# command. Doxygen will then run the mscgen tool (see
# the time of a run. So in most cases it will be better to enable caller
# graphs for selected functions only using the \callergraph command.
-CALLER_GRAPH = YES
+CALLER_GRAPH = NO
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
# will generate a graphical hierarchy of all classes instead of a textual one.
# HTML_FILE_EXTENSION to xhtml in order to make the SVG files
# visible in IE 9+ (other browsers do not have this requirement).
-DOT_IMAGE_FORMAT = png
+DOT_IMAGE_FORMAT = svg
# 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.
