@top_srcdir@/src/gras/Transport \
@top_srcdir@/src/gras/Virtu \
@top_srcdir@/src/xbt/ \
- @top_srcdir@/src/modules.doc \
- ./api_index.doc
+ @srcdir@/modules.doc \
+ @srcdir@/module-gras.doc \
+ @srcdir@/module-xbt.doc \
+ ./api_index.doc \
+ ./logcategories.doc
# 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
# directories that contain example code fragments that are included (see
# the \include command).
-EXAMPLE_PATH = @top_srcdir@/src/surf/ @top_srcdir@/examples/msg/
+EXAMPLE_PATH = @top_srcdir@/src/surf/ \
+ @top_srcdir@/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
# commands irrespective of the value of the RECURSIVE tag.
# Possible values are YES and NO. If left blank NO is used.
-EXAMPLE_RECURSIVE = NO
+EXAMPLE_RECURSIVE = YES
# The IMAGE_PATH tag can be used to specify one or more files or
# directories that contain image that are included in the documentation (see
# the \image command).
-IMAGE_PATH =
+IMAGE_PATH = @top_srcdir@/doc
# 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