* Generate a doxygen file with "doxygen -s -g"

=== What we typically change ===

 PROJECT_NAME           we have to choose a name
 OUTPUT_DIRECTORY       Use some directory under the Webserver's document root
 TAB_SIZE               = 4 is what we mostly want, 8 is the default

Pure C-Code should use the following options:

 OPTIMIZE_OUTPUT_FOR_C  = YES Not really sure what it does, but for pure C use it
 HIDE_SCOPE_NAMES       = YES   avoides lengthly struct_t::nMember

If we don't need to hide our sources we change the following

 EXTRACT_ALL            = YES
 EXTRACT_STATIC         = YES

==== and in the section "source browsing" ====

 SOURCE_BROWSER         = YES
 STRIP_CODE_COMMENTS    = NO
 REFERENCES_LINK_SOURCE = NO jumps to the function in the documentation file
                          YES links to the source code file

==== Output ====

 HTML_OUTPUT            subdirectory that will be created below OUTPUT_DIR
 HTML_STYLESHEET        = myDoxygen.css
 HTML_ALIGN_MEMBERS     = NO     (otherwise additional tables bloat the html)

 GENERATE_LATEX         = NO   (In most cases we don't need printed docs)
 USE_PDFLATEX           = YES  (But if yes, it would rather be .pdf, not .dvi)

==== Diagrams ====

 HAVE_DOT               = YES   (we want to use diagrams)
 
 CALL_GRAPH             = YES   (enable it only for smaller projects
                                For bigger projects try using \callgraph in the code)

* For C code better turn them off, they won't find anything

 GENERATE_LEGEND        = NO  Arrows allows means include(files) or call(functions)
 CLASS_GRAPH            = NO
 COLLABORATION_GRAPH    = NO
 MAX_DOT_GRAPH_DEPTH    = 7   (This depends highly on the type of code,
                               but if you keep the default 0, each and every graph
                               will have the custom-logger() function)