Ahhh, cmake and doxygen. The perfect combo to bitch about life for a
whole day...
-Edit (project)/buildtools/Cmake/DefinePackage.cmake, and add your
+Edit (project)/tools/cmake/DefinePackage.cmake, and add your
newly added page to the DOC_SOURCES. And bitch about these damn tools.
Don't forget to commit your page, so that you can get some git fun to
\section inside_doxygen_image Adding an image to the documentation
If you need to run a command (like fig2dev) to generate your image,
-edit buildtools/Cmake/GenerateDoc.cmake and add your command to the
-simgrid_documentation target (grep for fig2dev in the file to see
+edit tools/cmake/GenerateDoc.cmake and add your command to the
+doc target (grep for fig2dev in the file to see
where exactly). Don't forget to add the source of your image to the
archive somehow. You can add it to the list DOC_FIG of
-buildtools/Cmake/DefinePackage.cmake.
+tools/cmake/DefinePackage.cmake.
If your image is ready to use, put your png in doc/webcruft, and
register it to cmake by adding it to the DOC_IMG list of file
-buildtools/Cmake/DefinePackage.cmake so that it lands in the archive
+tools/cmake/DefinePackage.cmake so that it lands in the archive
distribution. It will also be copied automatically to the documentation.
\section inside_doxygen_website Working on the website
html output (and maybe the pdf too). Here is how to do this:
@verbatim
-make simgrid_documentation # html documentation
+make doc # html documentation
make pdf # the result is in doc/latex/simgrid_documentation.pdf
@endverbatim
