ADD_CUSTOM_COMMAND(TARGET dev_guide
COMMAND ${CMAKE_COMMAND} -E echo "XX First Doxygen pass"
COMMAND ${DOXYGEN_PATH}/doxygen DevGuideDoxyfile
- COMMAND ${CMAKE_HOME_DIRECTORY}/tools/doxygen/index_create.pl ../../shared/doxygen/simgriddevguide.tag index-API.doc
COMMAND ${CMAKE_COMMAND} -E echo "XX Second Doxygen pass"
COMMAND ${DOXYGEN_PATH}/doxygen DevGuideDoxyfile
INPUT = index.doc \
simgrid.doc \
xps.doc \
- cmake.doc
+ cmake.doc
###################################################
## PLEASE DON'T MESS WITH THE ORDER OF EXAMPLES ## (unless you know what you are doing, of course)
# directories that contain example code fragments that are included (see
# the \include command).
-EXAMPLE_PATH = ./ \
- @top_srcdir@/doc/gtut-files \
- @top_srcdir@/src/surf/ \
- @top_srcdir@/src/xbt/ \
- @top_srcdir@/examples \
- @top_srcdir@/testsuite
+EXAMPLE_PATH = ./
# 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
# NOT include the path). If a tag file is not located in the directory in which
# doxygen is run, you must also specify the path to the tagfile here.
-TAGFILES = ../../shared/doxygen/simgriddevguide.tag=../../dev_guide/html/
+TAGFILES = @CMAKE_HOME_DIRECTORY@/doc/shared/doxygen/simgriddevguide.tag
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
# a tag file that is based on the input files it reads.
-GENERATE_TAGFILE = ../../shared/doxygen/simgriddevguide.tag
+GENERATE_TAGFILE = @CMAKE_HOME_DIRECTORY@/doc/shared/doxygen/simgriddevguide.tag
# If the ALLEXTERNALS tag is set to YES all external classes will be listed
# in the class index. If set to NO only the inherited external classes
-/*! \page simgrid SimGrid Developer Guide - SimGrid
+/*!
+\page simgrid SimGrid Developer Guide - SimGrid
\section simgrid_dev_guide_api How to add a new MSG function?
\section simgrid_dev_guide_model How to add a new model in surf?